Thread: Touch Kobo lost ALL my books' read/unread status
View Single Post
Old 12-14-2012, 08:43 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 jusmee View Post
Running 2.1.5, my kobo just lost the read/unread status of ALL my books. Now it's so hard to find new books to read I think I will delete all my books and only ever load new ones onto the kobo, deleting them as I finish them, or decide they are no good, in case it does this again.

So annoying for software to be so unreliable.
I'm curious about what happened just before you lost the reading status. From my experience, this happens only when something goes wrong. Or using the old calibre driver.

The previous calibre driver set the reading status based on values in the tags column if the automatic metadata management was used. The current one doesn't for the Touch, Glo and Mini.

Another time you will lose the reading status is with a factory reset. There is nothing that stores the status for books other than kepubs, so the status can't be restored.

Another way to lose the status is if the database on the device gets corrupted. In that case, the device might rebuild the database after reprocessing the books on the device. The only times this has happened to me was been because I unplugged from the PC without ejecting it. The fix has always been to replace the database from a backup or do a factory reset. Logging off the device and back in again probably would have fixed it as well.

Logging off is another way to cause this. I believe this simply replaces the existing with an empty copy.

From the above, one way to reduce the problem is to take a backup of the database. This in ".kobo\KoboReader.sqlite". Then if it gets corrupted, restore the latest version. Then you only lose the changes since the backup was taken.
davidfor is offline   Reply With Quote