Thread: Elipsa Ghost eBook Purchase on an Elipsa
View Single Post
Old 07-17-2021, 10:08 PM   #23
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 Cootey View Post
I had DB Browser for SQLite already installed, so I copied the Elipsa KoboReader.sqlite and ran the "PRAGMA integrity_check" on it.

Code:
Execution finished without errors.
Result: 1 rows returned in 3144ms
At line 1:
PRAGMA integrity_check;
Because I backed up to an earlier version before things went kablooie, my database is fine.
Unfortunately, you will need to do this check each time. We don't know when the corruption is happening. I'm trying to eliminate calibre as the cause. Doing the check a few times should help with that.
Quote:
Running in debug mode now. Thanks.

I used Calibre to copy one book over and checked the database before ejecting. Everything is A-OK.



1) I don't have problems like this with either of our Kobo Clara HDs, or either Kobo Aura One in the past. I wasn't exactly paying attention to what I was doing just prior to getting the database error in Calibre, but IIRC, the error popped up when I plugged the Elipsa in after an evening of setup. That might indicate the problem happened on the Elipsa. I'll watch for it.
2) Powering off my Mac while the Elipsa is plugged in? No. I keep my Mac on at all times. I don't even let it sleep.
No I meant powering off the Elipsa. If it doesn't get shutdown properly, that could be a cause. And when the database is read, that can be when problems are noticed such as missing books and reading status.
Quote:
3) No log files as you described.
4) From what I've read, Mac tools for dealing with ExFat dirty drives is minimal. I'll have to see if that is the case if the corruption should occur again.
I have no idea what tools are available on the MAC for this, but I had a feeling that there wasn't much. Kobo did update dosfstools last year which solved some problems with the PC seeing the drive as dirty. I don't really expect this to be the problem, but it would be good to eliminate.
davidfor is offline   Reply With Quote