MobileRead Forums - View Single Post

talios · 09-05-2010, 06:43 AM

Last night I started noticing that whenever I powered on my Kobo reader it had forgotten the last page of the book I was on ( returning to a page I was previously at earlier ).

Thinking this may have been disk space related ( I had 8k free on the internal storage ) I moved about 200mb of ePub files to my external SD card, since then the units been stuck at "processing content" for several hours.

I managed somehow to reset it but putting a pin in the back and pressing random buttons, but now the unit just sits at "eReading: anytime, anywhere" as tho its starting up.

I don't seem to be able to power the unit down either.

I suspect the internal DB might have been corrupted ( and I seem to be seeing a few threads about that ) so am currently downloading the kobo-dir-fresh-1.4.zip file mentioned in other forums.

But before I start replacing DBs I was wondering if anyone else had seen a similar problem? Does this sound like a DB corruption issue?

09-05-2010, 06:43 AM	#1
talios Member Posts: 24 Karma: 14 Join Date: May 2010 Device: Kobo ereader	My Kobobrick? Last night I started noticing that whenever I powered on my Kobo reader it had forgotten the last page of the book I was on ( returning to a page I was previously at earlier ). Thinking this may have been disk space related ( I had 8k free on the internal storage ) I moved about 200mb of ePub files to my external SD card, since then the units been stuck at "processing content" for several hours. I managed somehow to reset it but putting a pin in the back and pressing random buttons, but now the unit just sits at "eReading: anytime, anywhere" as tho its starting up. I don't seem to be able to power the unit down either. I suspect the internal DB might have been corrupted ( and I seem to be seeing a few threads about that ) so am currently downloading the kobo-dir-fresh-1.4.zip file mentioned in other forums. But before I start replacing DBs I was wondering if anyone else had seen a similar problem? Does this sound like a DB corruption issue?