Quote:
Originally Posted by davidfor
That's the error shown when doing a manual check database. Are you getting a similar error from the driver when you connect? If so, it is probably not correctly showing the books that are on the device.
In any case, the error says the database is corrupt. And, it says the database is in such a bad state that it can't be checked. Usually, you get "Ok" or a list of errors. With a corrupt database, the device runs from the in memory copy of the data. It just can't write any changes to the database. If you power off, you will lose any changes. This can be the status of the books you are reading, annotations, shelve or the latest books added to the device. In the last case, it will reprocess the books each time. And if the database is bad enough that the device can't read it, it will throw it away and take you through the setup process to recreate it.
The fix for you is to restore a recent backup if you have one. If you don't you will need to signout on the device. The device will restart, and take you through the basic setup process. This includes recreating the database and then processing your sideloaded books.
|
Well, the device is all the time working without any issue; I wouldn't have suspected any problem without having done the "check database". Nevertheless, I remembered having tried to install Sergey's plugin some weeks ago - curiously without success. I desisted, removed the files that I had copied to the device and forgot about it. But there might have been something wrong.
Nevertheless, I'm inclined to wait with a reset or other changes until the next firmware update, unless there might come up some difficulty.
Thank you!