View Single Post
Old 05-02-2025, 07:09 PM   #16
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,308
Karma: 171295426
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
For a while when one firmware version was causing my Sage to suffer from database corruption on 1 in 4 connections, I used NickelMenu to trigger a reboot before connecting and to reconnect without needing to unplug. The reboot time was worth the time needed to restore the database.

The key for me was that every time calibre reported database corruption, looking in the .kobo directory on the Sage, I saw <databasename>.sqlite-wal (write ahead logging) and <databasename>.sqlite-shm (shared memory) files. When the database is closed, these file would be removed so this told me was that the Sage was not closing the databases before the USB connection was established. The reboot forced the database to close.
DNSB is offline   Reply With Quote