View Single Post
Old 09-01-2023, 12:18 PM   #145
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,076
Karma: 169815798
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by enuddleyarbl View Post
Well, I didn't pay attention and connected my Kobo Forma to Calibre without first rebooting the Forma. I was on the Home page, though. Immediate dirty bit/database error. Unfortunately, when I try using SQLite Expert Personal to fix things, it no longer works. There's still no Repair option under Database (which the Help file says should be there). And, the Vacuum option just pops up the error:

"database disk image is malformed SQL Statement: VACUUM."

The Check database function gives:

"database disk image is malformed SQL Statement: pragma integrity_check."

Any suggestions on how to get SQLite Expert Personal to repair the database?

It looks like the newest firmware (which may or may not be withdrawn) doesn't fix this (according to that thread). This has gotten very old, very fast.
The recover option is available in the Professional not the Personal version. You could try downloading the sqlite dll and tools from the SQLite Download Page. Also see Recovering (Some) Data From A Corrupt SQLite Database for the procedure.

OTOH, this is unlikely to work. A few years back, I tried recovery and then the Stellar Repair for SQLite tool. While both did recover most of the database data, when copied back to my Aura One, a factory reset was triggered. Most wasn't good enough.

And yes, my suggestion about using a NickelMenu entry to reboot before connecting to the computer is the only consistent solution I've found to connect without seeing .sqlite-wal and .sqlite-shm files indicating a database that was not closed before the connection.

Using the Kobo Utilities database backup is the best way to recover from a corrupted database.
DNSB is offline   Reply With Quote