I atried to perform an in place update but this failed too.
I would like to keep my configuration as I use 3 NAS Systems which are started using OSM WOL, an external database at an synology nas and some menue items containing filtered group of media. Not sure hwo I did configure this long time ago.
When reading the logs provided here I see the following error:
2025-06-06 19:05:04.253 T:936 error : SQL: [MyVideos131] The table does not exist
Query: SELECT idVersion FROM version
2025-06-06 19:05:04.253 T:936 error : Process error processing job
---------------------- Kodi Log END --------------- HyhIT4UP
Could it be that the mariaDb Database is no longer migrated as required due to the big version jump?
Any chance to do this manually?
OR should I create a new database? I do not mind to loose “viewed” information. And all details of my media are stored at the media folder anyway. So doing a new scraping / loading from disks would not be a problem - as long as the multiple mount points (nfs) are kept.
If this is a solution / try please advise how to create the new database while (at least until the new setup works) the old db is kept to use with old OSMC SD card.
EDIT:
Or would it be worth a try to migrate to some 2023 / 2024 releease - doing a stepby step migration.
Is there any place to grab older OSMC versions to do such an update?
Database MyVideos131 seems to be incomplete?
What do you think?
Should I delete MyVideos131 and try to start Kodi again? Will this eventually start a new migration?
Should I delete MyMusic83 too? (As I do not use OSMC to store music it will not be used anyway but I ask to ensure the best way to retrigger a migration / convertion)?
I’m guessing if there’s no MyVideos131, Kodi will create it and migrate the data from 119 and won’t care about MyMusic. I think @darwindesign uses MySQL and may know.
Correct. If Kodi does not find the current version database it will look for the previous version to update, and then failing that will look to see if there exists the previous one to that, and so on and so forth until it runs out of versions and then it will just make a new empty database. It works the same using MySQL as it does with a local database in this regard. The only potential difference that comes to mind is that a MySQL setup that used a name tag in advancedsettings.xml would have a different database name.
Check the version of Maria that your using against Kodi’s wiki on the topic. I think there is issues using too old of a version of Maria or MySQL with more modern version of Kodi.
If you drop or rename the database in Maria, or add/edit the database name tag in advancedsettings.xml then Kodi will automatically create a new empty database. If you have a current working setup you could in Kodi do a export to seperate files which would export your metadata including watched status. Importing watched status is now default so you don’t need to add that advancedsettings.xml anymore. One caveat with doing this is make sure you configure that same TV show scraper for TV shows as the old one. If the nfo files are pointed to TheTVDB and your scraper on the new setup is set to TMDB then those series will not scrape new episodes without some intervention.
I’ve dropped the incomplete database
I’ve created at new SD with 2024.08 Release.
I’ve startet 2024.08 release and configured it.
I restored the 2022.x backup
(After a long time) the system displayed some infos at TV. it stated i.e. that several plugins have been disabled. The databse was created correctly this time.
Then I started an search for update.
Update worked and system is now at 2025.03 (according to display at myOSMC).
NAS / Media Files seem to be reachable and working
So the next step will be to reactivate Metropolis and eventually other disabled plugins …
Thanks for feedback and do not spend timne for my problem any longer. I’ll drop a note if I need some more help.
