Thread: Suddenly Calibre doesn't mark some books on a Kobo Glo device
View Single Post
Old 05-10-2018, 08:12 PM   #35
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,907
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by bernard.ryefield View Post
I guess from KoboUtilities point of view it is, though from Kobo Glo point of view it isn't, which was my point.
The database is corrupt. But, a lot of the function on the device works from in-memory copy of the data. It doesn't need to constantly reread the data as most of the metadata is in memory. It will try to write the data to the database as things change, but these will probably fail. Then, if restart the device, it will attempt to read the database but all those updates will be missing and you will suddenly be seeing old data. And if the problems in the database are bad enough, the firmware can throw it away and start the setup process.

There is very little you can do to fix this. Sometime running a compress on the database will work. But, that usually only works if the errors are in an index. It can also work if the errors are elsewhere, but you usually lose some data. And if you lose data, there is probably some inconsistencies that could cause other problems.

This isn't going to get better. You need to fix it. If you have a database backup, you can restore that. Otherwise, you will need to do one of the things that DNSB suggested.
davidfor is offline   Reply With Quote