+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Jellyfin won't start: SQLiteException disk I/O error (/t-jellyfin-won-t-start-sqliteexception-disk-i-o-error)
Jellyfin won't start: SQLiteException disk I/O error - cryotek7 - 2023-10-22
Hi everyone,
Ran into an issue with my Jellyfin install. Runs on an LXC container on Proxmox, Jellyfin installed on one ZFS pool, media on another ZFS pool. Restarting the container does not fix issue. There are no issues with hard drive health or disk space. From searching online I read that this error can be caused by many different problems (some mentioned in this bug thread), and have been going around in circles. Any help appreciated.
[2023-10-22 13:43:58.007 +00:00] [INF] Jellyfin version: "10.8.3"
[2023-10-22 13:43:58.049 +00:00] [INF] Environment Variables: ["[JELLYFIN_LOG_DIR, /var/log/jellyfin]", "[JELLYFIN_CONFIG_DIR, /etc/jellyfin]", "[JELLYFIN_USER, jellyfin]", "[JELLYFIN_ARGS, $JELLYFIN_WEB_OPT $JELLYFIN_RESTART_OPT $JELLYFIN_FFMPEG_OPT $JELLYFIN_SERVICE_OPT $JELLYFIN_NOWEBAPP_OPT $JELLFIN_ADDITIONAL_OPTS]", "[JELLYFIN_RESTART_OPT, --restartpath=/usr/lib/jellyfin/restart.sh]", "[JELLYFIN_FFMPEG_OPT, --ffmpeg=/usr/lib/jellyfin-ffmpeg/ffmpeg]", "[JELLYFIN_CACHE_DIR, /var/cache/jellyfin]", "[JELLYFIN_DATA_DIR, /var/lib/jellyfin]", "[JELLYFIN_ADDITIONAL_OPTS, ]", "[JELLYFIN_WEB_OPT, --webdir=/usr/share/jellyfin/web]"]
[2023-10-22 13:43:58.058 +00:00] [INF] Arguments: ["/usr/lib/jellyfin/bin/jellyfin.dll"]
[2023-10-22 13:43:58.060 +00:00] [INF] Operating system: "Linux"
[2023-10-22 13:43:58.061 +00:00] [INF] Architecture: X64
[2023-10-22 13:43:58.063 +00:00] [INF] 64-Bit Process: True
[2023-10-22 13:43:58.063 +00:00] [INF] User Interactive: True
[2023-10-22 13:43:58.063 +00:00] [INF] Processor count: 2
[2023-10-22 13:43:58.063 +00:00] [INF] Program data path: "/var/lib/jellyfin"
[2023-10-22 13:43:58.064 +00:00] [INF] Web resources path: "/usr/lib/jellyfin/bin/jellyfin-web"
[2023-10-22 13:43:58.064 +00:00] [INF] Application directory: "/usr/lib/jellyfin/bin/"
[2023-10-22 13:43:58.415 +00:00] [INF] Setting cache path: "/var/cache/jellyfin"
[2023-10-22 13:43:58.450 +00:00] [INF] Loading assemblies
[2023-10-22 13:43:58.642 +00:00] [INF] Defined LAN addresses : "[10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]"
[2023-10-22 13:43:58.643 +00:00] [INF] Defined LAN exclusions : "[]"
[2023-10-22 13:43:58.644 +00:00] [INF] Using LAN addresses: "[10.0.0.0/8,172.16.0.0/12,192.168.0.0/16]"
[2023-10-22 13:43:58.660 +00:00] [INF] Using bind addresses: "[]"
[2023-10-22 13:43:58.660 +00:00] [INF] Using bind exclusions: "[]"
[2023-10-22 13:44:00.749 +00:00] [FTL] Error while starting server.
IOError: SQLitePCL.pretty.SQLiteException: disk I/O error
at SQLitePCL.pretty.SQLiteException.Throw(Int32 rc, Int32 extended, String msg)
at SQLitePCL.pretty.SQLiteException.CheckOk(sqlite3 db, Int32 rc)
at SQLitePCL.pretty.SQLiteDatabaseConnection.PrepareStatement(String sql, String& tail)
at SQLitePCL.pretty.DatabaseConnection.PrepareStatement(IDatabaseConnection This, String sql)
at SQLitePCL.pretty.DatabaseConnection.Execute(IDatabaseConnection This, String sql)
at Emby.Server.Implementations.Data.BaseSqliteRepository.GetConnection(Boolean readOnly)
at Emby.Server.Implementations.Data.SqliteItemRepository.Initialize(SqliteUserDataRepository userDataRepo, IUserManager userManager)
at Emby.Server.Implementations.ApplicationHost.InitializeServices()
at Jellyfin.Server.Program.StartApp(StartupOptions options)
[2023-10-22 13:44:00.762 +00:00] [INF] Running query planner optimizations in the database... This might take a while
[2023-10-22 13:44:00.948 +00:00] [INF] Disposing "CoreAppHost"
[2023-10-22 13:44:00.959 +00:00] [INF] Received a SIGTERM signal, shutting down
RE: Jellyfin won't start: SQLiteException disk I/O error - TheDreadPirate - 2023-10-22
Make sure that the permissions on the directory containing your database hasn't changed. This is usually caused by jellyfin not being able to read AND write the file.
Or possibly that the disk is full.