Thread: [GUI Plugin] Kobo Utilities
View Single Post
Old 10-21-2014, 10:59 PM   #670
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 melovesflying View Post
Hi! I don't know if it is just me but since upgrading to OS X Yosemite, I get a "failed backing up Kobo device database" alert whenever I connect my Kobo Aura to Calibre (I've set it to backup automatically once the reader is detected). Here are the details I got whenever I do so:



I'm quite positive that it has something to do with the new OS, since I was able to backup and sideload pubs just before I upgraded the OS. Is there a fix for this? What's weird is that when I go to KoboUtilities>Database>Backup Device Database, it works with no problem at all.
Those errors indicate the database is corrupt. My usual suggestion to fix this is to either restore a good backup of the database or do a logout and login on the device. The latter will generate a new database and then process all the books.

But, because all of the errors shown are related to an index, doing a compress of the database might fix it. I can't guarantee that it will work, but you won't be in a worse position afterwards than you are at the moment. Use the compress function in the plugin and then run the database check. If neither have an error, then it should be OK.

This shouldn't be related to the new OS, unless it isn't ejecting the device properly. Or is accessing it differently than before.

As to the manual backup not showing the errors, that is because it doesn't do the checking. The automatic backup checks the database after copying it to the PC. Hence you get this error and the file will have "CORRUPT" as part of the name. The manual backup simply copies the file. It was a quick and dirty solution I added a long time ago. I'll have to have a look at it.
davidfor is offline