[BensonBear]

Think I have to return my Kobo of nearly one month if they will take it back at Best Buy.

I have had many many problems with the very flaky software and poorly document interfaces and development tools but the most recent appears to be that the internal flash memory has become defective. After various innocuous operations the database was reported in the nickel output as being corrupted, and then the log I had it create was itself corrupted. I could not get things working again without an entire factory reset.

I could not always unmount the dos partition to check it for errors, despite killing nickel and not finding any other program that was accessing it. However sometimes I could, and it reported various errors, which it seemed to be able to fix. Also the dosfsck on my desktop system which I could run without mounting the filesystem would detect the same errors and it too could fix them.

But new errors quickly cropped up, just while attempting to read a book.

So I wiped out the file system on the dos partition and created another one. Things chugged along while I factory reset, installed 1.9.17 firmware, tweaks, content, fonts. Came up okay.

However, dosfsck reveals after this that the boot record and its backup do not match. That in the past was the first error that typically existed before the whole thing started looking bad.

The only explanation seems to be faulty flash memory, unless anyone else has any other idea in a day, I am going to take it back if I can. Given that I started from the beginning with a totally reformatted file system, and still got errors very soon, it seems unlikely to be software.

Not sure if I will get another despite being quite eager to see if I can get done what I was trying to.

Update: after this checking, read a bit of a book, went in and checked again, my desktop dosfsck finds error in KoboReader.sqlite, and indeed sqlite3 command line finds that it is malformed. Hardly anything was done to anything in the meantime.