|
Not every time, as I have been able, so far, to always perform the updates at the end. I've now adopted the habit of making a backup and checking the database is OK ("pragma integrity_check" with sqlitebrowser) before connecting to calibre. I've also checked the card and internal memory with dosfsck (no errors).
I always wait for the transfer to finish before updating the metadata, and for any task to finish before starting the next one, for what is worth. But I've had the same issue just with transferring books, no metadata update, so that's not the culprit. It seems to be a random event, I can't find any consistent cause, but there are a few variables that could be behind the issue and I don't always keep in mind (connecting from pure nickel, or from nickel within KSM; launching nickel from KSM right after booting, or after exiting a previous nickel session; mounting manually or letting calibre do it; trying to force a sync before disconnecting the device, or just clicking on "disconnect device" right after the transfer finishes...).
I've even had this happening:
- Connect the device to calibre: calibre reads the list of books, the plugin makes database backup. All fine.
- Select a few books, click on the plugin's "update database" menu, and bang! error message about a corrupted database.
- After restoring a previous backup and repeating the same actions, no problem at all.
I'm thinking there could be a problem with the cable or USB port, but I haven't had any issue when accessing the device outside calibre.
|