View Single Post
Old 11-11-2014, 12:05 PM   #15
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,476
Karma: 8025702
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by aceflor View Post
I can only remember a transfer between my laptop and my kindle fire done through CC going wrong (as in giving me the corrupt database message), ejecting the fire, exiting Calibre and not being able to start it again correctly.

Now that my library is rescued, I will need to empty the fire and refill it again. Probably not going to use CC this time around, and will not fill the fire before having done a backup of the library anyway.
What "corrupt database" message? CC doesn't have a message containing "corrupt" or its variants, so I am guessing that the message came from calibre.

The wireless driver that CC uses does not write the calibre database except under one condition: the "sync read information" column names have been filled in. In this case the driver uses the calibre database layer, just as the rest of calibre does.

Like eschwartz, I am interested in how the restore failure manifested itself. How did you know it failed? Were there error messages? Something else? I wrote that code, so if there is something broken I need to fix it.

Your problems "smell" a bit like they come from failing hardware. Have you checked that the disc in your computer is not going bad or that the file system is messed up? If not, you might want to schedule a full chkdsk (one that reads the entire disc) to see if there are bad spots. The same thing might be happening to the RAM in your machine. A memory tester would put that possibility to bed.
chaley is offline   Reply With Quote