Thread: [GUI Plugin] Kobo Utilities
View Single Post
Old 01-28-2015, 06:31 PM   #876
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
Hi, David!
All the time, the database check - and the database backup - worked well. There was no change in the firmware, reset or similar. However, in the last days, I always find this message after connecting the device to the computer:

Code:
calibre 2.17  isfrozen: True is64bit: False
Windows-7-6.1.7601-SP1 Windows ('32bit', 'WindowsPE')
('Windows', '7', '6.1.7601')
Python 2.7.9
Windows: ('7', '6.1.7601', 'SP1', 'Multiprocessor Free')
Successfully initialized third party plugins: DeDRM && Inept Epub DeDRM && Count Pages && Quality Check && Open With && Generate Cover && Modify ePub && Kobo Utilities && KePub Output && Resize Cover && KoboTouchExtended && Hyphenate This!
Traceback (most recent call last):
  File "calibre_plugins.koboutilities.action", line 1394, in check_device_database
  File "calibre_plugins.koboutilities.action", line 3140, in _check_device_database
  File "calibre_plugins.koboutilities.action", line 4365, in check_device_database
DatabaseError: database disk image is malformed
Is this dangerous? Can I do something? - Thank you for your help again!
That's the error shown when doing a manual check database. Are you getting a similar error from the driver when you connect? If so, it is probably not correctly showing the books that are on the device.

In any case, the error says the database is corrupt. And, it says the database is in such a bad state that it can't be checked. Usually, you get "Ok" or a list of errors. With a corrupt database, the device runs from the in memory copy of the data. It just can't write any changes to the database. If you power off, you will lose any changes. This can be the status of the books you are reading, annotations, shelve or the latest books added to the device. In the last case, it will reprocess the books each time. And if the database is bad enough that the device can't read it, it will throw it away and take you through the setup process to recreate it.

The fix for you is to restore a recent backup if you have one. If you don't you will need to signout on the device. The device will restart, and take you through the basic setup process. This includes recreating the database and then processing your sideloaded books.
davidfor is offline