[Cootey]

Alright. I'm back with another database corruption. For the record, I never have these issues with my Kobo Clara.

I believe that the recent firmware updates released for the Kobo have improved things. I've gone 22 days without a database corruption—until earlier this morning. Unfortunately, I did not remember to quit Calibre before ejecting as you had suggested (something I had been forgetting to do recently), but I do have more information that might help us.

My notes on my latest Elipsa glitch:

1. Checked database using Kobo Utilities in Calibre. ✔
2. Imported about 21 manga through Calibre. Database ✔
3. Imported another 9 manga. Checked database again. It was corrupt.
4. On a whim, I deleted all 30 manga manually off the Elipsa before ejecting it from desktop. This avoided the import/database destruction I’ve noticed in the past. All purchased books remained downloaded. No re-importation of all previously imported books occurred.
5. Repaired Kobo account. Plugged Elipsa back into Mac. Checked database. It remained corrupt.
6. Backed up my .nebo journal files, then I restored from older backup via Terminal. This has ALWAYS worked before, but this time…
7. …Elipsa .jpg & .svg files (the stylus notations and their page screenshots) from the .kobo/markups directory were now loaded as individual files. Several Kobo pages worth in My Books. Even repairing the account didn’t properly categorize them. I thought perhaps they might be newer out of sync annotations that weren't part of the older database, but the rsync string I use to restore a backup deletes everything off the Elipsa that isn't present in the backup.
8. Logged out of my account on my Kobo, then logged back in. Markup files were still listed individually as "books". I checked the database with Kobo Utils plug-in in Calibre, and the database had been repaired as expected. Since I wasn’t sure which markup files were being categorized correctly and which were not, I…
9. Did a factory reset (with current firmware).
10. Annotations were restored. I don't know if I lost any, but I keep WiFi on all the time, so it's not likely. (Turns out I lost annotations from just the past 24 hours before corruption.) Database is not corrupt. I'm ready to rebuild my setup again. But I've lost time, I'll be losing more time getting things back up and running, and I'm grumpy about it. Why is this happening to my Elipsa? ����*♂️

Here are my observations. I’ve used Calibre to import manga before since the last Elipsa database corruption with no issues. Yet whenever the database is corrupted, Calibre seems to be involved. (I run Calibre in debug mode, so please tell me what you folks need to see to help identify what is happening. I'll send it to you since it likely contains names of my local drives and network). When I sideload hundreds of books by dragging and dropping onto the mounted Elipsa, I have ZERO database issues.

I did notice, however that the Elipsa was constantly being ejected this morning. THIS behavior is consistent with corruption events. Whether I was plugged into a hub or directly into the back of my 2014 Mac Mini, the Elipsa would connect, then suddenly eject itself. This is very irregular behavior, and the Elipsa was the only device having this issue. The Mac did not display any warning dialogues as it usually does if you unplug a USB device without ejecting through the Finder first. That seems to indicate that it was rejected properly. When the Elipsa seemed to be stably connected for a few minutes, I imported the manga through Calibre. The Elipsa was not ejected during this process. However, after the transfer was complete (done in two steps BTW with me checking the database after each batch) the database was corrupt after the second, smaller batch. Then I did step 4 above to minimize the damage, but to no avail.

After resetting the firmware, my Elipsa was connected for half a day without being ejected from my Mac. I can make sure that I quit Calibre and Kobo Desktop in the future. I have put in an order for a different USB hub. But neither of those things may be the problem. In the meantime, something became corrupt on that second Calibre batch. The Elipsa hadn't technically imported anything yet since it was still mounted to my desktop. I'd like to figure this out. I'm not the only person running into corrupt database issues with the Elipsa.

The following is the PRAGMA integrity check when I discovered the database was corrupt. I don't think this is any different than any other integrity check dump that I've shared. It just means the database is now corrupt:

Spoiler:

Result of running 'PRAGMA integrity_check' on database on the Kobo device:


*** in database main ***
On tree page 54734 cell 0: invalid page number 167909888
Page 52133: btreeInitPage() returns error code 11
Page 52134: btreeInitPage() returns error code 11
Page 52132: btreeInitPage() returns error code 11
On tree page 52116 cell 0: Rowid 47480 out of order
On tree page 52116 cell 0: invalid page number 84037120
On tree page 52171 cell 1: Rowid 47546 out of order
On tree page 52171 cell 1: invalid page number 167772160
On tree page 52171 cell 0: invalid page number 167836416
On tree page 54521 cell 35: Rowid 45054 out of order
Page 52177: btreeInitPage() returns error code 11
On tree page 29598 cell 91: 2nd reference to page 50413
On tree page 29598 cell 91: Child page depth differs
On tree page 29598 cell 90: Child page depth differs
On tree page 759 cell 7: Rowid 28237 out of order
On tree page 761 cell 1: Rowid 47659 out of order
On tree page 762 cell 1: Rowid 47644 out of order
On tree page 11685 cell 10: 2nd reference to page 15476
On tree page 2578 cell 2: Child page depth differs
On tree page 2578 cell 1: Child page depth differs
On tree page 12703 cell 3: 2nd reference to page 20888
On tree page 51982 cell 3: 2nd reference to page 7442
On tree page 51982 cell 2: 2nd reference to page 52151
On tree page 51982 cell 1: 2nd reference to page 52153
On tree page 51982 cell 0: 2nd reference to page 684
Page 52009: btreeInitPage() returns error code 11
On tree page 42540 cell 0: 2nd reference to page 46433
On tree page 42540 cell 5: 2nd reference to page 46348
On tree page 42540 cell 4: 2nd reference to page 46308
On tree page 42540 cell 3: Child page depth differs
On tree page 7572 cell 2: invalid page number 218103808
On tree page 2978 cell 1: Rowid 1526 out of order
On tree page 54756 cell 1: Rowid 47600 out of order
On tree page 54756 cell 1: 2nd reference to page 1099
On tree page 54756 cell 0: 2nd reference to page 54764
On tree page 2304 cell 2: invalid page number 218103808
On tree page 2309 cell 1: Rowid 1221 out of order
On tree page 51860 cell 1: 2nd reference to page 1179
On tree page 50331 cell 0: Rowid 1438 out of order
Page 2310: btreeInitPage() returns error code 11
Page 50332: btreeInitPage() returns error code 11
On tree page 3874 cell 1: Rowid 1135 out of order
On tree page 3873 cell 0: Rowid 1133 out of order
On tree page 3872 cell 0: Rowid 1132 out of order
On tree page 3871 cell 1: Rowid 1131 out of order
On tree page 52237 cell 4: invalid page number 218103808
Page 54754: btreeInitPage() returns error code 11
Page 370 is never used
Page 498 is never used
Page 529 is never used
Page 615 is never used
Page 630 is never used
Page 631 is never used
Page 1227 is never used
Page 2301 is never used
Page 2812 is never used
Page 2972 is never used
Page 2974 is never used
Page 2975 is never used
Page 2976 is never used
Page 2977 is never used
Page 3038 is never used
Page 3321 is never used
Page 6416 is never used
Page 6519 is never used
Page 6525 is never used
Page 6527 is never used
Page 6528 is never used
Page 6529 is never used
Page 6530 is never used
Page 6532 is never used
Page 6534 is never used
Page 6535 is never used
Page 6536 is never used
Page 6537 is never used
Page 6538 is never used
Page 6540 is never used
Page 6543 is never used
Page 6544 is never used
Page 6546 is never used
Page 6547 is never used
Page 6549 is never used
Page 6550 is never used
Page 6551 is never used
Page 6552 is never used
Page 6553 is never used
Page 6577 is never used
Page 6825 is never used
Page 11226 is never used
Page 11399 is never used
Page 11407 is never used
Page 11551 is never used
Page 49819 is never used
Page 49824 is never used
Page 49826 is never used
Page 49832 is never used
Page 49837 is never used
Page 49844 is never used
Page 49845 is never used
Page 49849 is never used