Thread: Aura HD and Calibre: DatabaseError: database disk image is malformed
View Single Post
Old 04-06-2014, 03:06 PM   #5
jackastor
Wizard
jackastor ought to be getting tired of karma fortunes by now.jackastor ought to be getting tired of karma fortunes by now.jackastor ought to be getting tired of karma fortunes by now.jackastor ought to be getting tired of karma fortunes by now.jackastor ought to be getting tired of karma fortunes by now.jackastor ought to be getting tired of karma fortunes by now.jackastor ought to be getting tired of karma fortunes by now.jackastor ought to be getting tired of karma fortunes by now.jackastor ought to be getting tired of karma fortunes by now.jackastor ought to be getting tired of karma fortunes by now.jackastor ought to be getting tired of karma fortunes by now.
 
jackastor's Avatar
 
Posts: 1,847
Karma: 3212428
Join Date: Jun 2011
Device: iphone stanza, kobo touch,ASUS TF300,KOBO GLO, Kobo Aura HD, Kobo Mini
Quote:
Originally Posted by rantoie View Post
I'm getting this error when I connect my device and launch calibre:

database disk image is malformed

Traceback (most recent call last):
File "/usr/lib/calibre/calibre/gui2/device.py", line 86, in run
self.result = self.func(*self.args, **self.kwargs)
File "/usr/lib/calibre/calibre/gui2/device.py", line 490, in _books
mainlist = self.device.books(oncard=None, end_session=False)
File "/usr/lib/calibre/calibre/devices/kobo/driver.py", line 1764, in books
for i, row in enumerate(cursor):
DatabaseError: database disk image is malformed

I saw somewhere that I should try a reset. The procedure seems to be to power off the device, stick a paperclip in the hole and then the device should reset. That doesn't happen when I put the paperclip in the hole.

I am apprehensive of doing a full factory reset, I've done a lot of hacking on this device, getting ssh access, setting up koreader and the launcher, changing various settings etc. If I factory reset, I'm going to loose all of that, aren't I?
To ensure you don't have this issue again and again, always make sure you eject your device and wait for the computer/software to proper eject it b4 removing the device. Failure to do so will result in this error repeatedly over and over.

regards

Jack
jackastor is offline   Reply With Quote