Quote:
Originally Posted by franklekens
Thank you, and others for any tips.
I'm not quite sure I understand what this "reading list" is? Is it a feature in Calibre?
|
This is the Reading List plugin... also I use the Smart Eject plugin to automatically check for sync and run the searches before ejecting.
Quote:
Anyway, I was grumbling before I actually did the reboot on the Sage. When I tried re-sideloading my books in batches of 500 at a time,
[...]
And I noticed that the device seemed to rebuild it database by itself, althought it seemed to need a few reboots to do it, it couldn't do it all in one go.
|
I've had that issue too. It seems to time out while scanning large numbers of books. I'm not sure if it's an extra large book in the batch or just the large number of books overall. I have eliminated a few books from the device because I thought they were causing problems, but it still takes two or three reboots to get through them all. Side loading in smaller batches does help, but then you have a higher chance of recorrupting the database. (Rebooting between loads might help.)
Quote:
|
I had lost all my reading progress on the books I'd been reading *and* any annotations/highlights &c I had added.
|
I also have the Kobo extended driver plugin and the Kobo Utilities plugin.
The latter can save and restore your reading positions. Unfortunately, there is no functionality to save and restore annotations on side loaded books.
If forgot that got lost on reset.
I haven't had a major database corruption in a month or two.
I am still having issues though -- something keeps the database open (sometimes sync, sometimes maybe the reader, sometimes neither but something else), but Calibre has been detecting it instead of messing with the database and warning me. Then I eject and reboot the kobo and reconnect and all is fine.
In the past, when I had database corruption, I have restored from backup and rebooted and it was fine, but I haven't had to do that since I upgraded to the latest version of Calibre. I probably haven't had to rebuild the database from scratch in at least 4 months, and I haven't had to re-sideload all my books since I discovered I could just delete a corrupted database to get it to rebuild. (Alas, this loses annotations.)