SOLVED: can't start jellyfin after disk full

[Cremator]

I had the same issue, and I could fix it fairly easy. I am using lsio jellyfin docker.

1. Stop the bad jellyfin container:

Code:

docker stop jellyfin

2. Start a new jellyfin container:

Code:

docker run -d --name=new-jellyfin -e PUID=1000 -e PGUID=1000 -e TZ=Europe/Sofia -v /tmp/new-jellyfin:/config lscr.io/linuxserver/jellyfin:latest

3. Dump the new-jellyfin migrations table into a sql file:

Code:

sqlite3 /tmp/new-jellyfin/data/data/jellyfin.db
sqlite> .output /tmp/mytable_dump.sql
sqlite> .dump __EFMigrationsHistory
sqlite> .quit

4. Drop and recreate __EFMigrationsHistory in the bad jellyfin:

Code:

sqlite3 /var/lib/docker/volumes/bad_jellyfin/_data/data/data/jellyfin.db
sqlite> drop table __EFMigrationsHistory;
sqlite> .read /tmp/mytable_dump.sql
sqlite> .quit 

5. Copy migrations.xml from new to bad:

Code:

cp /tmp/new-jellyfin/migrations.xml /var/lib/docker/volumes/bad_jellyfin/_data/migrations.xml

6. Start the bad, hopefully now good jellyfin container:

Code:

docker start jellyfin