View Single Post
Old 01-15-2013, 07:46 PM   #11
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 problem is the errors seen in the first post. The database on the device became corrupted. As Windows also found a problem with the file system, it most likely means the device was unplugged from a PC without being ejected properly. Until those were fixed, things wouldn't work properly.

With a corrupted database, the device can continue working, but it becomes "forgetful". The tendency is for the database to get stuck at a certain point and connecting to the PC or restarting the device loses the state. So you can read a book and it tracks the position, but power off and it goes back to unread or where you were up to when the problem occurred.

Fixing the file system and database was the solution. The logout replaces the database with an new copy, so that fixes things in most circumstances. The books are then added back to the database and library lists. I've seen the problem about them not being added immediately after a logout/login. It looks like it might recover the kepubs first, and then after another connect to USB or a power off, it scans for the other books.
davidfor is offline   Reply With Quote