2024-12-06, 06:48 AM
(This post was last modified: 2024-12-06, 07:00 AM by ponyboy. Edited 1 time in total.)
I seem to have found an issue with Jellyfin's handling of changing/removing library locations.
I have Jellyfin installed via docker, and during an update accidentally changed the internal mount location of my media drive, i.e. "/Movies" to "/drives/Movies"; and for whatever reason (I'm still not sure why) instead of simply changing the mount location back, I changed Jellyfin to point to the new location for my media folder by adding a second Movies library with the new location, and then removed the old library. After realizing my mistake, I changed the docker mount back to the original location and changed my Jellyfin library location back to the original. While everything works as originally now, and my media is now mounted correctly; I now have an issue that every Movie in my library that is part of a collection appears as a collection, even if there is only one movie in that collection, despite my settings requiring 2 movies within a collection to create it. When looking within my library.db file; in the typedbaseitems table, there is still two copies of each movie, one with the currently used path e.g. "/Movies/A Movie (2024)/A Movie (2024).mp4"; and the other with the path that no longer exists, and no longer has a library e.g. "/data/Movies/A Movie (2024)/A Movie (2024).mp4". While replacing collection metadata and deleting the offending single movie collections seemed to work at first, this was not the case. It seems upon the scheduled task for scanning library for new box sets all of the single movie collections are recreated. I would appreciate any help that can be given, and I hope that this may help find if there is potentially an issue with the way that Jellyfin handles the additon + removal of libraries
I have Jellyfin installed via docker, and during an update accidentally changed the internal mount location of my media drive, i.e. "/Movies" to "/drives/Movies"; and for whatever reason (I'm still not sure why) instead of simply changing the mount location back, I changed Jellyfin to point to the new location for my media folder by adding a second Movies library with the new location, and then removed the old library. After realizing my mistake, I changed the docker mount back to the original location and changed my Jellyfin library location back to the original. While everything works as originally now, and my media is now mounted correctly; I now have an issue that every Movie in my library that is part of a collection appears as a collection, even if there is only one movie in that collection, despite my settings requiring 2 movies within a collection to create it. When looking within my library.db file; in the typedbaseitems table, there is still two copies of each movie, one with the currently used path e.g. "/Movies/A Movie (2024)/A Movie (2024).mp4"; and the other with the path that no longer exists, and no longer has a library e.g. "/data/Movies/A Movie (2024)/A Movie (2024).mp4". While replacing collection metadata and deleting the offending single movie collections seemed to work at first, this was not the case. It seems upon the scheduled task for scanning library for new box sets all of the single movie collections are recreated. I would appreciate any help that can be given, and I hope that this may help find if there is potentially an issue with the way that Jellyfin handles the additon + removal of libraries