Apologies for dragging up an old thread but kinda wish I'd found this thread earlier. Had assumed my SSD had failed a few months back, resorted to running from USB for a while. Decided today to replace the SSD but was unable to install to it. Damn thing would boot installer but SSD not found by the installer. Tried the run option and that worked, using the SSD as storage, so restored the backup I made from the USB I had going and all was back OK, albeit booting with the run option. My OCD got the better of me and I tried chewitt idea of editing the boot option on the original SSD, it worked!!! bought a goddam new SD for nothing.
Posts by ElGato
-
-
OK, so where does this file need to be on Pi4, struggling to find location. Just bought a new G20 and have this issue, strange thing is I have an existing G20 I've had for a couple years and it's OK
-
Finally, two days later, I succeeded in updating to V8 using the mysql database. Obviously the problem occured as a result of an interrupted migration process before. From that time on from this I wasn't able to re-connect to the database again.How did I succeed in the end?
1. Downgrading to 7.0.3
2. Soft Reset of 7.0.3
3. Deleting all parts of Krypton db inside the KODI-environment
(version 107 of video db - could be MyVideos107 or xbmc_video107 or whatever your special name-tag in advancedsettings.xml defines,
version 60 of music db - could be MyMusic60 or xbmc_music60 or whatever your special name-tag in advancedsettings.xml defines,
Addons27.db)
4. if necessary dropping V8-databases in the environment of mysql-server
(version 107 of video db - could be MyVideos107 or xbmc_video107 or whatever your special name-tag in advancedsettings.xml defines,
version 60 of music db - could be MyMusic60 or xbmc_music60 or whatever your special name-tag in advancedsettings.xml defines)Starting from this cleaned up state, next time the database migration worked as designed. Updating the other clients to V8 there was no problem any more to connect immediately to the migrated database.
Seems my issue was the existence of the v107 videos database, maybe as a result of trying v8 beta's previously, once this was removed the database upgrade completed as expected.