Jellyfin removes all movies that are on unmounted drives

[kitt]

The situation looks like this: 

I have two libraries. Once I delete one of them (or rename it), Jellyfin refreshes the libraries with an automatic scan - even if I disable not checking for live changes. After that all movies that are on drives that are not mounted in macOS are gone. Without a backup I would have to retag a lot of movies...

I can reproduce this since I have a backup. Every time I delete the other library Jellyfin removes the movies.

If I manually refresh all libraries this does not happen. It makes sense that it keeps these movies.

How can I avoid this?

[TheDreadPirate]

I don't think you can. Removing a library triggers a library scan, by design. AFAIK, that is not configurable.

When you say "manually refresh all libraries" I assume you mean you refresh the libraries individual instead of clicking "Scan all libraries".

[kitt]

Yes, but the weird thing is that this does not delete all my movies from the database. I can refresh as often as I want. If I understand correctly, Jellyfin detects that the drive is not available rather than removing the content. Somehow this refresh that is triggered automatically is different - and probably a nasty bug.

I can fix this by mounting my hard drives for now, but I would rather understand the behavior.

I do daily backups, but this would be a nightmare because I edit all my movie fanarts.

[TheDreadPirate]

This sounds like this bug.

https://github.com/jellyfin/jellyfin/issues/15343

Which has been resolved in Jellyfin 12.0.

[kitt]

I am tempted to try v12 RC7. I have backups, but I am wondering if I run into trouble once the final release of Jellyfin is released. Or shouldn't that be a problem? Going back to 10.11.11 is not possible due to a new database if I understand correctly.

I do get some weird bugs in the current stable so I might as well go to an RC.

Note: Fixed indeed in RC7. However JS Injector and other plugins seem to be disabled/not working? Do I have to do something? I guess they should be compatible by now, right?

[TheDreadPirate]

Those plugins are 3rd party and it is up to their respective developers to provide compatible version. Check their gits to see if they've provided any "unstable" versions to test with the JF 12 RC's.

For the official plugins, you need to remove the "stable" plugin repo and add the "unstable" plugin repo, which contains JF 12 compatible plugin updates. Once JF 12 is officially released the "stable" repo will need to be re-added and unstable removed.

https://repo.jellyfin.org/files/plugin-u...ifest.json

[kitt]

Thanks, I am now on v12 and will adapt. File Transformation is the only thing I am missing, but I think I can work around this by substituting MDBList Ratings with Jellyfin Enhanced.

Before I really commit to v12: Will my database still work in the final version of v12 or should I go back to the backup? I ask because I want to know if it makes sense to further optimize my database wehen I have to reset in a few weeks.

[TheDreadPirate]

Always have backups, but 12 RC# to stable 12 is a supported upgrade path.