![]() |
Updated Synology 7.1 Docker Container to use NAS shares - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: General Questions (https://forum.jellyfin.org/f-general-questions) +--- Thread: Updated Synology 7.1 Docker Container to use NAS shares (/t-updated-synology-7-1-docker-container-to-use-nas-shares) |
Updated Synology 7.1 Docker Container to use NAS shares - samatusen - 2025-04-17 After moving Container to use a folder on the NAS vs internal docker path, the refresh metadata is failing, Updated all the permissions but the docker seems to still look at old location. MediaBrowser.Controller.Entities.BaseItem: Error refreshing owned items for "/config/root/default/Movies" System.IO.DirectoryNotFoundException: Could not find a part of the path '/config/root/default/Movies'. RE: Updated Synology 7.1 Docker Container to use NAS shares - TheDreadPirate - 2025-04-17 From the container's perspective, there shouldn't be any change in path. You address that by updating the container volume mapping. Which folders did you move to the NAS? /config and/or /cache? If so, /config should never be on a NAS since that is where the Jellyfin database is located. At a minimum, /config/data should remain on a local disk. RE: Updated Synology 7.1 Docker Container to use NAS shares - samatusen - 2025-04-17 Yessir that is what I did. I was unable to get existing container to pull the latest. So I made file share for the /cache and /config and then mounted them to the container as new file path so that it didn't matter what container connected as the config would be outside the container. Copied all the contents over and then chown/chmod the new folders in the duplicated container. For the duplicated container I exported the settings first and then just imported them thinking that it would pick up the the new path to find it's config but by the log I do not think that is actually happening? I do not have the Container Manager and using Docker, but assumed there is some config file somewhere where I need to update these path's? Or you just saying I need to now copy back over all the files back into the container? I do not think it would be performance issue as it is the same network connection as the box, and for last couple days have not seen any performance issues for the libraries that were already discovered, so is that really a worry having them on the NAS vs inside of the container? Code: "env_variables" : [ [2025-04-16 04:35:04.330 +00:00] [ERR] [35] MediaBrowser.Controller.Entities.BaseItem: Error refreshing owned items for "/config/root/default/Photos" System.IO.DirectoryNotFoundException: Could not find a part of the path '/config/root/default/Photos'. at System.IO.Enumeration.FileSystemEnumerator 1.Init() 1.Init()at System.IO.Enumeration.FileSystemEnumerableFactory.FileSystemInfos(String directory, String expression, EnumerationOptions options, Boolean isNormalized) at System.IO.DirectoryInfo.InternalEnumerateInfos(String path, String searchPattern, SearchTarget searchTarget, EnumerationOptions options) at MediaBrowser.Controller.Providers.DirectoryService.<>c.<GetFileSystemEntries>b__5_0(String p, IFileSystem fileSystem) at MediaBrowser.Controller.IO.FileData.GetFilteredFileSystemEntries(IDirectoryService directoryService, String path, IFileSystem fileSystem, IServerApplicationHost appHost, ILogger logger, ItemResolveArgs args, Int32 flattenFolderDepth, Boolean resolveShortcuts) at MediaBrowser.Controller.Entities.CollectionFolder.CreateResolveArgs(IDirectoryService directoryService, Boolean setPhysicalLocations) at MediaBrowser.Controller.Entities.CollectionFolder.GetFileSystemChildren(IDirectoryService directoryService) at MediaBrowser.Controller.Entities.BaseItem.RefreshMetadata(MetadataRefreshOptions options, CancellationToken cancellationToken) [2025-04-16 04:35:04.341 +00:00] [ERR] [44] Emby.Server.Implementations.ScheduledTasks.TaskManager: Error executing Scheduled Task RE: Updated Synology 7.1 Docker Container to use NAS shares - TheDreadPirate - 2025-04-17 All I see is that you changed the data paths within the container. Not how they are stored on the host. Which would 100% break jellyfin. RE: Updated Synology 7.1 Docker Container to use NAS shares - samatusen - 2025-04-19 Ok so do I just need to copy all of the files back and instead point the /config and /cache at the NAS. Understand there are performance concerns with that. RE: Updated Synology 7.1 Docker Container to use NAS shares - TheDreadPirate - 2025-04-19 Ideally /config in its entirety would be on local storage. At a minimum, /config/data should be on a local disk since that contains the database. The rest would be ok, but suboptimal, to put on the NAS due to the number of small requests. Network file systems are not built for numerous small transfers. RE: Updated Synology 7.1 Docker Container to use NAS shares - samatusen - 2025-04-19 I tried copying back the files to /config and /cache, setting mount point to those directories and Jellyfin doesn't load. Switched back now to mount points that were working and now nothing loads. Am I just broke now and lost all of Jellyfin config? RE: Updated Synology 7.1 Docker Container to use NAS shares - samatusen - 2025-04-19 Thanks, triggered thoughts of folder directories, and I forgot to marry up config with mount points. Update both to be the same and appears all working again. |