2 hours ago
Hey all!
I originally posted this in the Matrix troubleshooting chat, but it looks like the forum is the preferred place to get help so here I am. 😇
When updating from 10.10.7 to 10.11.2, the database migration fails with this error:
I have a backup and downgraded back to 10.10.7 for now so all is fine, but I'd like to be able to update... at some point 🙃.
This is an instance that's been gradually updated over 10+ years from a really old emby version all the way to Jellyfin 10.10.7 (so far, amazingly, without problems!), so there's probably all kinds of weird relics in the database... 🤣
I'm SQL/sqlite-savvy but not fluent in C# (know other C-family languages though), and of course happy to help contribute a fix (or at the very least help track down the underlying problem) for any potential others with this issue. (Though it's probably rare...? A quick search didn't find any similar cases so far at least...)
I've included the full logs of both the first update attempt and the last run attempt (with the partial update completed) as attachments, both trip over the same thing as far as I can tell.
If there's anything else I can do or provide to help debug this, please do let me know. I should be responsive to replies here.
Finally: I'm impressed with (and offer my thanks for) the neat way the system prevents data loss during the update. I initially didn't notice the update had happened (it was part of a general system update) and the careful way the migrations preserve old versions of databases until complete allowed me to restore the pre-update state perfectly (which I then immediately backed up, of course!). Well done! 👏 Would've ended terribly for me had that all not been in place, many thanks for that. 👍
I originally posted this in the Matrix troubleshooting chat, but it looks like the forum is the preferred place to get help so here I am. 😇
When updating from 10.10.7 to 10.11.2, the database migration fails with this error:
Code:
[2025-11-11 12:47:53.195 +01:00] InternalCodeMigration: Error: "Must specify valid information for parsing in the string. (Parameter 'value')"
[2025-11-11 12:47:53.195 +01:00] InternalCodeMigration: Migration "20250420200000_MigrateLibraryDb" failed
System.ArgumentException: Must specify valid information for parsing in the string. (Parameter 'value')
at System.Enum.ThrowInvalidEmptyParseArgument()
at System.Enum.TryParseByValueOrName[TUnderlying,TStorage](RuntimeType enumType, ReadOnlySpan`1 value, Boolean ignoreCase, Boolean throwOnFailure, TUnderlying& result)
at System.Enum.Parse[TEnum](String value, Boolean ignoreCase)
at System.Enum.Parse[TEnum](String value)
at System.Linq.Utilities.<>c__DisplayClass2_0`3.<CombineSelectors>b__0(TSource x)
at System.Linq.Enumerable.ArraySelectIterator`2.Fill(ReadOnlySpan`1 source, Span`1 destination, Func`2 func)
at System.Linq.Enumerable.ArraySelectIterator`2.ToArray()
at Jellyfin.Server.Migrations.Routines.MigrateLibraryDb.GetItem(SqliteDataReader reader)
at Jellyfin.Server.Migrations.Routines.MigrateLibraryDb.Perform()
at Jellyfin.Server.Migrations.Stages.CodeMigration.Perform(IServiceProvider serviceProvider, IStartupLogger logger, CancellationToken cancellationToken)
at Jellyfin.Server.Migrations.JellyfinMigrationService.InternalCodeMigration.PerformAsync(IStartupLogger logger)
at Jellyfin.Server.Migrations.JellyfinMigrationService.MigrateStepAsync(JellyfinMigrationStageTypes stage, IServiceProvider serviceProvider)I have a backup and downgraded back to 10.10.7 for now so all is fine, but I'd like to be able to update... at some point 🙃.
This is an instance that's been gradually updated over 10+ years from a really old emby version all the way to Jellyfin 10.10.7 (so far, amazingly, without problems!), so there's probably all kinds of weird relics in the database... 🤣
I'm SQL/sqlite-savvy but not fluent in C# (know other C-family languages though), and of course happy to help contribute a fix (or at the very least help track down the underlying problem) for any potential others with this issue. (Though it's probably rare...? A quick search didn't find any similar cases so far at least...)
I've included the full logs of both the first update attempt and the last run attempt (with the partial update completed) as attachments, both trip over the same thing as far as I can tell.
If there's anything else I can do or provide to help debug this, please do let me know. I should be responsive to replies here.
Finally: I'm impressed with (and offer my thanks for) the neat way the system prevents data loss during the update. I initially didn't notice the update had happened (it was part of a general system update) and the careful way the migrations preserve old versions of databases until complete allowed me to restore the pre-update state perfectly (which I then immediately backed up, of course!). Well done! 👏 Would've ended terribly for me had that all not been in place, many thanks for that. 👍
