Quote:
Originally Posted by davidfor
How much time was between these? It shouldn't matter, but, see my comment on item 10.
|
Immediately after each step. I didn't wait. I cannot recall how long it took for each upload job.
Quote:
Originally Posted by davidfor
I don't know about this. I don't have an Elipsa to play with, so I don't know what to expect. The images being imported as "books" means that the device saw them as books. Is it possible you got the directory name wrong? Nothing under ".kobo/markups" should be imported. If you made a typo with the name, it would explain it.
…That is consistent with point 7. It really does sound like the files were in the wrong place.
|
I don't know what to tell you. I was as surprised as you are. It should not have happened. I never meddled with the contents of the .kobo folder. I would never arbitrarily change the name of a folder inside .kobo. Until I get my Elipsa to behave, I haven't even installed NickelMenu. The only additions I have made have been screensaver photos, custom dictionaries, and fonts.
Quote:
Originally Posted by davidfor
But, I suspect that annotations sync stopped when the database became corrupted. That's why I asked about the time between notes 2 and 3. If there was some time between them, the corruption might have happened shortly after the first books were imported. But, you didn't see it until the trying to import the next set of books.
|
Since I checked the database between importation jobs, not pausing long between jobs, it seemed clear to me that the corruption occurred during or after the second batch.
Quote:
Originally Posted by davidfor
But, how do you know? The reason you know about the database corruption is that calibre discovers it. All that tells you is that between the last time and this time, something happened. And even that isn't accurate. Unless the problem is really bad, calibre will only report a problem if the parts it accesses have problems. Getting the list of books reads two tables. If there are no problems with those tables, then no error will be reported. But, if there are problem elsewhere, things could be going wrong elsewhere. And maybe they will affect the part that calibre usually sees later. This is why I sometimes tell people to check the database.
|
This is why I have been asking for how to share the debug logs with you—so that we can better determine which process (Mac, Calibre, Kobo, etc) is causing this database corruption.
Quote:
Originally Posted by davidfor
But, the basic problem is that calibre does not treat the Elipsa differently to any other Kobo device. If calibre is the cause, why aren't we seeing the same problem with all devices?
What else was going on? Did you have calibre or something else running that would have been accessing the device?
|
I use the same setup with my Clara and have
never had this problem. This has only been an issue for my Elipsa (both the original and its replacement).
Quote:
Originally Posted by davidfor
That really just tells me that the database is corrupted an it is unlikely to be recoverable. The only times I have found that corrupt databases have been recoverable is when the problems are only in the indexes or they are only freespace errors. It won't harm to try a VACUUM, but, I expect you will get an error during this and it won't be able to complete.
|
Yes, but why is it corrupting? That's what I need help identifying. (I don't see "VACUUM" in the database submenu of KoboUtils). I know that other people in this forum have had database corruption issues with their Elipsas. At least one or two returned their Elipsa because of it. Where would I find the debug logs that you need to see?