2025-07-20, 08:04 AM
I don't know how to fix it without rescanning but I would suggest for the future you switch to saving the metadata in .nfo files, that way jellyfin will store a small text .nfo file as well as a thumbnail next to each video with all the metadata so any edits are preserved. that way you can just backup the video folders and all the info will be backed up.
There is a slight downside to using .nfo files, since they are stored next to your videos and the videos are probably on a regular hard drive you sometimes have to wait 2 or 3 seconds for the drive to wake up before the thumbnails load.
The initial scan will probably be fairly fast a few minutes if it realizes it is the same content but different location but even redownloading the metadata maybe an hour at worst for a large library.
You may not want to do this but you could give the new network share location the same pc name, share name etc. and directory structure as your old location and just rename your old one, that should fool jellyfin into thinking it's the same and preserve your edits.
There is a slight downside to using .nfo files, since they are stored next to your videos and the videos are probably on a regular hard drive you sometimes have to wait 2 or 3 seconds for the drive to wake up before the thumbnails load.
The initial scan will probably be fairly fast a few minutes if it realizes it is the same content but different location but even redownloading the metadata maybe an hour at worst for a large library.
You may not want to do this but you could give the new network share location the same pc name, share name etc. and directory structure as your old location and just rename your old one, that should fool jellyfin into thinking it's the same and preserve your edits.