MobileRead Forums - View Single Post

davidfor · 11-15-2021, 07:15 PM

I assume that message is coming from calibre. But, that's only because I don't know of anything else that access the device database and can check. If you don't have a backup of the database to restore, then this will usually be fixed by signing out of the Kobo account on the device an back in. That will create a new database, add the books from Kobo and and sideloaded books. Unfortunately, it means losing the readings status and annotations for sideloaded books. If this doesn't work, then you might need to do a factory reset.

The database can be repaired under some circumstances. If it is only the indexes that are corrupt, or some free space, then doing a compress, or more correctly, an SQLite VACUUM, can fix things. There are options in my Kobo Utilities plugin to check the database and do the check and the compress.

11-15-2021, 07:15 PM	#2
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	I assume that message is coming from calibre. But, that's only because I don't know of anything else that access the device database and can check. If you don't have a backup of the database to restore, then this will usually be fixed by signing out of the Kobo account on the device an back in. That will create a new database, add the books from Kobo and and sideloaded books. Unfortunately, it means losing the readings status and annotations for sideloaded books. If this doesn't work, then you might need to do a factory reset. The database can be repaired under some circumstances. If it is only the indexes that are corrupt, or some free space, then doing a compress, or more correctly, an SQLite VACUUM, can fix things. There are options in my Kobo Utilities plugin to check the database and do the check and the compress.