Advice for Jellyfin users that want to upgrade to 10.11.0 from 10.10.7 or lower…
This is a massive update with a ton goin on in it. Learn from my mistake.
BEFORE UPDATING:
- BACKUP your Jellyfin sever/instance.
- SHUTDOWN your Jellyfin instance
This update will migrate your data to a new SQL format. If Jellyfin is using the SQL data during the update, it will LOCK the database file…and you will never regain write access again. No amount of uninstalls and reinstalls can fix it
I was using the Jellyfin right from the linuxserver.io repo, not from the casa repo. I’m assuming the update wasn’t vetted for Zima/Casa before the repo offered up the update (the one from Casa is still on 10.10.7, even though its still from linuxserver.io I think). I have since switched to using the Jellyfin from the Casa repo.
Although, my media was untouched, I lost my Jellyfin server and had to start from scratch. I tried all suggestions from the internet to resurrect the old database, to no avail. Jellyseerr, Jellystat and jfa-go also all broke. I was able to save Jellyseerr and Jellystat. Jfa-go had to be started from scratch again. This ends up being quite a bit of work with 25 users to add and configure and also tell them that all their watchlists and watch progress is gone.
Jellyfin 10.10.7 is just fine. I wish I had chosen to wait on the update. 3 days to get everything working again.
Don’t do what I did.