Quote:
Originally Posted by MGlitch
Presuming it’s a corrupt database from 4.31, wouldn’t the issue persist in 4.32 until the database was remade? Since OP can “fix” the issue by loading a single book which then reveals all the books already on the device?
|
The symptoms do not actually suggest a corrupt database. I had something like it a couple of times when the books partition was mounted as readonly. When I ejected the device, it would import most of the sideloaded books but, it could not actually update the database. Restarting the device would restore everything with no damage apart from the the rude words muttered under my breath.
Quote:
Originally Posted by poczynek
Ah right.
Yes sorry to clarify, I am on the latest firmware and it happened in the firmware prior.
What is the best way to remake the database?
|
If it is a corrupt database, then the best thing is to sign out of the Kobo account on the device. When you sign back in, a new database will be generated and the sideloaded books imported. That will mean the loss of reading status and annotations for the sideloaded books. But, as I said above, the database might not be corrupted. As you use calibre, it may give an error when you connect about the corrupted database. Or you can use my Kobo Utilities plugin to do a full check of the databases. It can also backup the database to help recover from issues in the future, or store the reading status of your books to be restored.