+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Deleted Media still in system (/t-deleted-media-still-in-system)
Deleted Media still in system - Lukas Lindner - 2024-01-13
Hey there
I rearranged my folder structure a little bit a few days ago ro make it more consistent and suitable for Jellyfin. Jellyfin rescanned the library and found every film again, so far so good.
But when I take a look at the logs, I can see that there are numerous log entries that warn me that the films that I moved could not be found on their old locations.
It looks for example like this:
[WRN] [57] MediaBrowser.Controller.Entities.BaseItem: Unable to find linked item at path "/media/.... and so on
They appear with every new library scan and also if I navigate to - for example - collections etc.
I guess, with the first library scan after restructuring the folders, the films in question got added again as a new item, but the old items never got removed from the system.
It is not problematic as the user experience is not diminished by that. Everything works fine and I see every film just once as it should be.
But I still would like to have system integrity.
Does anyone have a fix for this?
Jellyfin Version: 10.8.13 (latest)
Running on Docker (Container Manager) on my Synology DS 920+ (Operating System: Linux, Architecture: X64)
Thank you
P.S.: Sorry if there already is a thread about this.. I did not found it.
RE: Deleted Media still in system - TheDreadPirate - 2024-01-13
If you had a playlist or collection of movies/shows before you move their location, those playlists/collections will still be looking at the previous location.
RE: Deleted Media still in system - Lukas Lindner - 2024-01-14
Ok, the problem was because the deleted items before were linked to collections.
Items that are no longer present in the file system for some reason are still present in the metadata for the collections. (*)
Instead of deleting the whole collection and manually re-creating it (what I guess would have worked, too) I edited the config/data/collections/YOUR COLLECTION [boxset]/collection.xml file and removed all <CollectionItem>-Tags that hold a path that does no longer exist.
After a library scan (and I threw in a database and cache cleanup, just to be safe) the error logs are gone and I still have the collections as they were.
* I guess there is a cleanup of the collection xml files missing in the script that removes items while not found on file system during a library scan