View Single Post
Old 11-30-2014, 09:28 PM   #4
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 Chris_Snow View Post
Thx David,

Took me a while to find that sign out bit, but seems to be working as I type. I guess it's rebuilding a new db (its taking its time - only 15% done).
For different reasons, I've done this a couple of times in the last few weeks. It's at least an hour to load the 1200 sideload books I have on it. The one thing I like about doing a factory reset is it forces me to do a cleanup of the books on the device.
Quote:
I figured all the issues stemmed from the corrupt db
Yes. But, I suspect the database has been corrupt for a while. The device can run for a while with a corrupt database. Most of the work is done using the in-memory data structures and failures to write to the database don't affect that. It's only when it has to reload from the database that it has problems. That happens after a restart of the device.
davidfor is offline   Reply With Quote