+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: can't start jellyfin after disk full (/t-solved-can-t-start-jellyfin-after-disk-full)
RE: can't start jellyfin after disk full - m0ngr31 - 2024-11-05
(2024-08-10, 07:45 AM)Cremator Wrote: 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
I was able to follow this and got Jellyfin to come up again, but I can't login with any of my users. Is there a way I can restore that?
RE: can't start jellyfin after disk full - TheDreadPirate - 2024-11-05
We'd need to see your logs. Share them via pastebin.
RE: can't start jellyfin after disk full - m0ngr31 - 2024-11-05
(2024-11-05, 09:42 PM)TheDreadPirate Wrote: We'd need to see your logs. Share them via pastebin.
There's nothing in the logs - it thinks everything is normal. But if I peek in the
jellyfin.db database, the Users table is empty. I've tried some various things, but right now I deleted jellyfin.db and tried to run the migrations again (removing *.old` off of the already migrated databases), but that didn't do the trick either.I get these kinds of messages when it tries to start now: https://pastebin.com/qsN3uHQ7
It had some other messages when it was running the migrations, but I can't get those in Unraid anymore. I'd have to start the process over again.
RE: can't start jellyfin after disk full - TheDreadPirate - 2024-11-05
Open a terminal window for unRAID, navigate to where you are mounting /config. In that folder will be another "config" directory, delete or rename system.xml and migrations.xml and restart the container.
RE: can't start jellyfin after disk full - m0ngr31 - 2024-11-05
(2024-11-05, 10:56 PM)TheDreadPirate Wrote: Open a terminal window for unRAID, navigate to where you are mounting /config. In that folder will be another "config" directory, delete or rename system.xml and migrations.xml and restart the container.
Okay, I tried that. I get this in the log about the migration: https://pastebin.com/Pz4w7EdY
It's still not migrating the Users. I can see that
activitylog.db.old is created though, so at least that one was migrated at least
RE: can't start jellyfin after disk full - TheDreadPirate - 2024-11-05
I think your database is borked. The db output file you mentioned may be for debugging purposes.