+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: New Media Source Won't Scan (/t-new-media-source-won-t-scan)
RE: New Media Source Won't Scan - KodiUser1138 - 2024-09-07
Was hoping to have more info on a possible solution. I keep checking google and the like but have yet to find anything that might address why none of the methods I can come up with work to add a new source path since JFv10.
RE: New Media Source Won't Scan - Hectik - 2024-09-07
By new Media source I assume you mean new Library? What is your set-up? hosting through docker, baremetal or windows?
Maybe jellyfin doesn't have permissions to the files and media inside the new library you are trying to add.
RE: New Media Source Won't Scan - KodiUser1138 - 2024-09-07
(2024-09-07, 01:51 AM)Hectik Wrote: By new Media source I assume you mean new Library? What is your set-up? hosting through docker, baremetal or windows?
Maybe jellyfin doesn't have permissions to the files and media inside the new library you are trying to add.
A new source added to an existing library, a new network path to a new storage location through Windows 10. The same as all my other media locations that have worked fine prior to JFv10. JF has full access to all other locations and this new location works fine on the LAN and through other programs and systems. Even directly using the folder on the same local machine the JF server runs fails to add any items to the library. Nothing has worked short of killing this version and reverting back to JFv9. Almost all the contained media was previously scanned without issue into JF in other network locations before needing to reconfigure some storage and create a new drive shared folder location.
RE: New Media Source Won't Scan - TheDreadPirate - 2024-09-07
Can you describe your setup? I've seen bits and pieces here and there. But could you summaries your storage situation?
How many hosts with network shares? What OS for each? SMB protocol versions? Are they all using the same user names, permissions, etc.
RE: New Media Source Won't Scan - KodiUser1138 - 2024-09-07
My system breakdown as follows.
MainPC - Windows 10, My MS profile/passwords - working PC - location of Jellyfin Server.
Movies 3 - Shared Folder used for Mounted Hard drive
Movies 3B - Shared folder on hard drive with other things on it
Movies 4 - Shared folder on hard drive with other things on it (the problematic one)
TV Shows 11 - Shared Folder used for Mounted Hard drive
Other Movies - Shared hard drive with 3 folders used for certain "movie" content (not porn).
Media - Shared hard drive with several folders used to organize music and Apple compatible versions of movies for IOS devices
Additional shared drives and folders
MediaServer1 - Windows 10, My MS profile/passwords - Main Kodi client
AEW - Shared Folder used for Mounted Hard drive
Movies 1 - Shared Folder used for 10 Mounted Hard drives
Movies 1B - - Shared folder on hard drive with other things on it
TV Shows 101 - Shared folder on hard drive with other things on it
D: - Shared hard drive with several folders used to organize certain media for Jellyfin/Kodi
MediaServer2 - Windows 10, My MS profile/passwords - Secondary Kodi Client
Movies 2 - Shared Folder used for 4 Mounted Hard drives
TV Shows - Shared Folder used for 10 Mounted Hard drives
That is my current setup while I work on a new vault system that will house all hard drives used for my media library and a system dedicated to just running my Jellyfin server. Every share listed above has worked in JF prior to needing to add the Movies 4 location to move around some storage space. Each of the shared folders have either mounted drives or separate folders by type and letter as part of further organization. So example \\MAINPC\Movies 4\Blu-ray Movies Z\Zack and Miri Make a Porno (200
Bluray 1.78\All shares/folders were added to JF prior to v10 through Dashboard/Libraries/Manage Library where the pop up menu gave to text boxes to enter the media path. The top box, when populated, would return all subfolders in that path and allow you to select down further is needed. The lower box said something about share directory, I can't really remember, but I always filled both boxes with the same share path. Now that lower box is gone in v10.
When attempting to add a new location in v10 and putting the path for my new location into now the only text box available I again see it populated with all subfolders and allows further navigation. This is no matter what manner I enter the path, the SMB share, the computer direct folder, the SMB shared folders mounted as a hard drive, nothing works. 1 shared path, 4 sub-folders, 44 total media folders, JF can't see to add any of them.
RE: New Media Source Won't Scan - TheDreadPirate - 2024-09-07
(2024-09-07, 04:58 AM)KodiUser1138 Wrote: When attempting to add a new location in v10 and putting the path for my new location into now the only text box available I again see it populated with all subfolders and allows further navigation. This is no matter what manner I enter the path, the SMB share, the computer direct folder, the SMB shared folders mounted as a hard drive, nothing works. 1 shared path, 4 sub-folders, 44 total media folders, JF can't see to add any of them.
This paragraph seems contradictory. You see the subpaths but can't add them? Or are you not navigating to the subpath?
From my test Windows setup.
\\192.168.1.3\library is mounted to drive letter "O". Add "O:\Anime Movies" (equivalent to \\192.168.1.3\library\Anime Movies) to a library. Are you attempting to add the whole share to a library?
RE: New Media Source Won't Scan - KodiUser1138 - 2024-09-07
I can navigate to the subfolders meaning JF is seeing the shared folder/drive and is capable of accessing it within the dashboard/libraries/manage libraries popup box. I don't need to navigate further into the folder for the other shares that are setup in this manner. Everything is setup and accessible in the same manner within JF and all the sources that were added prior to JFv10 scan all sub folders without issue. Only the 1 newly added source location fails.
If the changes to JFv10.9 mean I can't have one main folder where I can mount/hold sorted subfolders that then contain the curated media folders and instead have to add every individual main folder containing only the individual media folders it takes library management backwards in ease of use. I already had to do that for TV shows where my root TV Shows folder share that has 10 mounted hard drives as subfolders wouldn't scan further down so each of those 10 folder shares are added as individual sources.
But even if I add the new shared folder right down to the individual letter so what appears in the list box is all the directories for each individual movie, JF still fails to scan and add those movies to the library. Nothing works at this point in JFv10.9.3. I've been mis-remembering which JF versions I've used and JFv10.8 didn't have these issues, only since 10.9.
RE: New Media Source Won't Scan - KodiUser1138 - 2024-09-09
Still haven't resolved this. Currently unable to add any new source path of any type to an existing Movies library.
RE: New Media Source Won't Scan - TheDreadPirate - 2024-09-09
You don't need to add the folder for each movie, but you would have to add each parent folder. IIRC there was one for each letter in your setup? Nesting folders has never been officially supported, though it sometimes worked.
RE: New Media Source Won't Scan - KodiUser1138 - 2024-09-09
Nested folders worked fine for movies prior to v10.9. Now nothing works. Not adding the direct main folder path on the same PC as the server, not a network share folder, not a mounted drive from a network share folder, nothing.
\\MainPC\Movies 4\ doesn't work
\\MainPC\Movies4\Blu-ray Movies Z\ doesn't work
z:\Movies 4\Blu-ray Movies Z\ doesn't work
Z:\Blu-ray Movies Z\ doesn't even return the list of subfolders
And all this further goes to my points about collections, if suddenly all the file paths need to change in your library then all your collections will be empty and worse if you can't manually edit the XML files to have them re-scanned to fix things quickly.
So many new issues making things more difficult and less functional despite the improvements in newer versions.