Thread: Clara HD Error: database disk image is malformed
View Single Post
Old 11-08-2020, 06:17 PM   #6
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 retro View Post
That's the same error I've been getting. Despite resetting, reimaging and restoring the db, it keeps coming back.

compurandom mentioned he thinks calibre is corrupting the db on his forma but going to 5.x might have fixed it. I'm trying that now.

https://www.mobileread.com/forums/sh...d.php?t=334262
Here's the problem with reports like that from @compurandom; there is no evidence of the claim. My problem is that I know what calibre does. I know what the driver does. And I can, when working on the driver or one of the plugins, testing beta firmware or testing a problem reported here, plugin one of my devices and let calibre see it hundreds of times in a day. That is not an exaggeration. And do you know how often I see database corruption? Maybe twice a month. And, every time I can track it to something I did. Mostly I bumped the cable at the wrong time. The socket in my laptop is a little worn, and in a terrible position.

As to you thread in general, you kept bringing up the second database on the device, "BookReader.sqlite". An I kept telling you that it had nothing to do with it as calibre does not touch it. If you truly believe it was corrupt and causing calibre to detect that the database was corrupt, then you have demonstrated without a doubt that calibre is not what is causing the database corrupt. Calibre, or more specifically the KoboTouch and KoboTouchExtended drivers, do not touch this file and do not have any knowledge that it exists. If something is corrupting this file and the main database, then it is not calibre.

One last thing, for your thread, the location that the corruption was detected was in code reading the database. At that point, calibre has not done anything other than open the database to read it. It is unlikely that reading the database would corrupt it. It is most likely that it was corrupted sometime before this. If it was calibre causing the problem, it would have been the previous connection. In which case you should have seen an issue while using the device. Especially if you restarted it at some point.
davidfor is offline   Reply With Quote