Thread: [GUI Plugin] Kobo Utilities
View Single Post
Old 04-18-2020, 07:19 AM   #1768
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Leonatus View Post
Windows 10, 32 bit, Calibre 4.13, KU v. 2.11.0, Kobo Touch A.
I recently get this message at plugging the device in:
Code:
calibre, version 4.13.0 (win32, embedded-python: True)
Failed to backup device database: Fehlgeschlagen: Backing up Kobo device database


wrong # of entries in index content_bookid_index
wrong # of entries in index sqlite_autoindex_content_1

Traceback (most recent call last):
  File "site-packages\calibre\gui2\device.py", line 90, in run
  File "calibre_plugins.koboutilities.jobs", line 197, in do_device_database_backup
Exception: 
wrong # of entries in index content_bookid_index
wrong # of entries in index sqlite_autoindex_content_1
In fact, I yesterday added a book to Calibre and then to the device (SD card). But the book itself seems to be o. k. EpubCheck etc. and Calibre Check show no issues.
And on my other computer (Windows 10, 46 bit), there was no problem. I just can't test it once more, because the other computer is at a different place.

Can somebody help, please?
The error message means that something has happened to the database to corrupt it. How that happened, I don't known. A common reason is not ejecting the device properly. But, it has nothing to do with a particular books or any error a book.

If you are swapping between two computers, the error should happen on both. But, if it happened on one yesterday, and the other today, it just means that the corruption happened in between. Possibly when you were disconnecting from the first.

My usual advice for fixing a corrupt database is to restore a backup, or do a signout and back in on the device. But, the errors show are in the some indexes. These can be fixed. Doing a compress will rebuild the indexes. And I think the firmware will do this at some point, but, I'm not sure when. The plugin has a compress function. Try that, disconnect and reconnect and see if it fixes it.
davidfor is offline