Thread: Elipsa New Kobo (N604) [Elipsa - ed.]
View Single Post
Old 07-03-2021, 09:40 AM   #600
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 anacreon View Post
I've had multiple problems with the Elipsa database since I have it, as I've explained in detail elsewhere
Spoiler:

I had hoped now the DB is more or less stabilized, it would stop, but no! Since I saved it yesterday evening, it should be more or less painless, but I'd like to understand.
So here is this morning's error message
Spoiler:
CorruptError: database disk image is malformed

Traceback (most recent call last):
File "calibre\gui2\device.py", line 89, in run
File "calibre\gui2\device.py", line 515, in _books
File "calibre\devices\kobo\driver.py", line 1974, in books
apsw.CorruptError: CorruptError: database disk image is malformed

And here the result of Kobo Utilities' DB check:


Furthermore I can't open any of the PDFs I was happily reading on Elipsa, while the kepubs work fine. I suppose it is linked with the DB problems.

Can somebody explain what might be happening, so I could understand and prevent it recurring again and again?
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.
davidfor is offline   Reply With Quote