View Single Post
Old 07-03-2021, 12:11 PM   #603
anacreon
Guru
anacreon ought to be getting tired of karma fortunes by now.anacreon ought to be getting tired of karma fortunes by now.anacreon ought to be getting tired of karma fortunes by now.anacreon ought to be getting tired of karma fortunes by now.anacreon ought to be getting tired of karma fortunes by now.anacreon ought to be getting tired of karma fortunes by now.anacreon ought to be getting tired of karma fortunes by now.anacreon ought to be getting tired of karma fortunes by now.anacreon ought to be getting tired of karma fortunes by now.anacreon ought to be getting tired of karma fortunes by now.anacreon ought to be getting tired of karma fortunes by now.
 
anacreon's Avatar
 
Posts: 978
Karma: 3475832
Join Date: May 2012
Location: France
Device: Elipsa, Sage, Libra 2
Quote:
Originally Posted by davidfor View Post
The errors tell me that the database has been corrupted. The messages from check says it is corrupted in ways that it cannot be recovered. Or at least I don't know of a way to recover it.

The database is being corrupted because something is going wrong. What, I have no idea, just something is preventing the database from be written correctly. It can happen when you don't eject the device correctly at the wrong time. It would also happen if the process updating the database had crashed without the the database being save properly.

It could be calibre. I would not expect so, but, there could be something new on the device that disagrees with calibre. To check that, you would need to test the database before using calibre. You can do that from any SQLite database management tool. And check again after using calibre before ejecting.

It could also be some interaction with your PC. Testing with another PC would help to check this.

It could be a hardware problem. As it seems to be happening continuously for you, that is likely. I don't think I have seen another report of a problem with the database on an Elipsa.

Other than doing some of these tests, and keeping track of what you are doing so that you can see a pattern for when it happens, I don't have any suggestions. You can contact Kobo and they could ask for a log file to look at. That gets produced in developers mode. Unfortunately, it is now encrypted so we can't look at it. Or, they might decide it is a hardware problem and exchange it.
Reading you and rantaplan, I'm starting to think that the problem is with Elipsa or its cable. I tried using other USB-C cables, and they don't work, just as Elipsa's cable doesn't work with other devices, so I can't test the cable. And my PC (a Surface Book 2 15" with bells and whistles) works fine with the Forma and Libra. Of course, there are many more books on the Elipsa, notably those I can't read on smaller Kobos, but neither of you points at problems issuing from books. And since I have the Elipsa (24 June), I synchronize Elipsa and Libra (the 4200 items present on both) every morning, since I read on the Elipsa at home, and the Libra outside.

So I probably should contact Kobo, but I won't be home for more than 2 weeks at a time until the end of September, so I will do it then. I'll have to save the database very often meanwhile, but I don't want to miss the pleasure of reading on Elipsa books I couldn't read comfortably before. And they mostly are big books I have more time for on holidays.

Last edited by anacreon; 07-03-2021 at 12:13 PM.
anacreon is offline   Reply With Quote