I did eject safely, but what I did notice is that the Kobo didn't do the usual post-eject "Importing new content" (or whatever the message is.) I thought because I had deleted and replaced the same book with the same file it wasn't necessary, so I didn't think much about it. Then when I plugged it in the next time I had the problem.
Quote:
Originally Posted by ownedbycats
Any chance that you had disconnected without safely ejecting first? I believe Kobo uses FAT32 filesystems, which do not like sudden interruptions. I've corrupted my DB and some books a few times from it.
It's also possible that it's just a regular old bad block in the memory and it was touching both the DB and your specific book file. The good news is that it should mark that block as unusable and leave it alone.
|