Quote:
Originally Posted by incumbent
Yeah there is *but it's not descriptive.
Just says there was a problem reading the device information or what-have-you and then show details doesn't give any real identification of an issue other than can't find a database it doesn't tell me where it looked.
That's why I use the Database Compress or some other action that will give a more verbose error message.
|
But, any earlier can error invalidate anything that happens later. It is possible that the reason it is trying to access the SD card here is because something broke earlier that confused things.
Quote:
Boo. Question *do you or anyone know what calibre-related files ought to be on the SD card? The reason I ask is that my SD card has, aside from books and PDFs and comics:
Code:
koboExtStorage/
metadata.calibre
driveinfo.calibre
|
The "koboExtStorage" directory is put there by the firmware. The others are put there by calibre. These two files should also be in the main memory of the device. Are they?
Quote:
`driveinfo.calibre` contains
Code:
{"location_code": "main", "device_name": "Kobo Aura HD", "calibre_version": "2.43.0", "device_store_uuid": "(obfuscated)", "last_library_uuid": null, "date_last_connected": "2015-11-11T02:39:48.500774+00:00", "prefix": "/Volumes/KOBO16/"}
|
That's wrong. But, whether that is the cause or a symptom, I cannot tell. Is it possible you copied this file there from the devices main memory? If so, that might cause it. In any case, delete both the "metadata.calibre" and "driveinfo.calibre" and see if calibre is happier.
Quote:
|
`find . -type f | wc -l` says I've got 2546 files on the card. I don't know what is normal or abnormal for processing the files on a card but I'll time it for science right now.
|
Quote:
Originally Posted by incumbent
Pulled the SD card after ejecting volumes, plugged it back in, Calibre was fine. Didn't whine about the database or anything. I just don't keep books there really except some news feeds that I didn't clean up yet. (I hate when the database blows up and I have to reinitialize the device so I made that as painless as I could by putting all my books and stuff on the SD card so I don't have to copy it all back.)
Eject successful, Kobo comes back up to Nickle or whatever, and I insert the card with no new books on it since the last time I managed it successfully.
Time to complete: About 60 seconds. Fumbled with the card a bit so give or take 5 seconds.
|
That's sort of what I expected. It would be better if it was faster, but it's not slow enough that it would bug me.
Quote:
Plugged it back in for Calibre and
crickets:
 ERROR__Error, on Flickr
Same drill. If I attempt a database operation it's def trying to hit the card and not the internal storage.
|
OK, that is from the initial connect and is the first time the database is accessed. Anything later is uninteresting at this point as this is what has to be fixed.
Unfortunately, it doesn't tell me much. As jgoguen suggested a few posts ago, a debug log is needed to see what is happening. Restart calibre in debug mode, connect the device and let the connection jobs run. When the error happens, close calibre and post the complete log. From that, I can get a better idea of what is happening.
And just to be clear, this is not a problem with the extended driver. This is in the underlying KoboTouch driver or the calibre code to handle devices. Or it could be something strange about the device or the way the OS (Mac?) is presenting the device. And it is the first time I have heard of a problem like this.