Thread: Kobo Glo keeps getting corrupt database when using Calibre
View Single Post
Old 06-08-2016, 10:37 AM   #3
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
The initial connection jobs taking a long time can be a sign that the database is corrupt. It depends on exactly where in the database the problem is as to whether it shows up during these jobs. Can you post the details of the error message? Exactly what and were in the driver the error is displayed can give some hints about what is happening.

As to the cause, I've never had proof that the driver can cause a corruption of the database. Usually, it is something else such as not ejecting the device properly. I've also seen corruption after a crash of the device, or a freeze followed by pressing the reset button to restart the device.
davidfor is offline   Reply With Quote