Thread: Error communicating with device
View Single Post
Old 06-24-2016, 10:05 AM   #6
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by MerlinMama View Post
Ok. Following that brings up another question:

Wouldn't the 'corrupt' database be what your PI backs up or are there multiple backups? Here's why I ask:
The backup can be set to keep a number of copies. When the backup is done, the oldest version is removed. But only after checking that the lasted backup is not corrupt. If the latest backup is corrupt, the file is renamed to include "CORRUPT" to separate it from the good backups. If you need to restore the database, you use the newest backup that is not corrupt.
Quote:
Although it proclaimed an error, Calibre still showed the device as connected. When I tried sending a book, just to check, it again brought up the error message. That's all good. When I signed out and it rebuilt the database, the book I had tried sending WAS on the device (I didn't notice it sending and it's too late to check now). To my way of thinking, the device did in some form connect to Calibre, so a backup of the corrupt database would have occurred, if I'd been using the PI.

Did that make any sense? I'm not sure anymore, I'm confusing myself LOL. I'll leave this as is for now, and hope you understand what I'm trying to say.
That is expected behaviour. The corrupt database prevents calibre from doing some things and that depends on how the database is corrupt. The driver is queries one table to work out what books are on the device. If that part of the database is corrupt, then calibre can't do this. The error you are seeing is when the driver attempts to update the series info and collections. In either case, calibre can still copy a book to the device. It cannot do the database updates, such as create collections when sending the books, but the book will be there for the device to process.
davidfor is offline   Reply With Quote