View Single Post
Old 09-23-2024, 04:58 PM   #47
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,134
Karma: 169815798
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by compurandom View Post
I'm getting database corruption with calibre on this firmware again, so I'm going back to rebooting before connecting via usb. I've had to reset the database twice this week, and the second corruption was pretty massive. I couldn't even repair by dumping the database.
Could I ask you to check if when you connect your LC to your computer without the reboot, if in the .kobo directory, you see files with names such as BookReader.sqlite-wal, BookReader.sqlite-shm, KoboReader.sqlite-wal and KoboReader.sqlite-shm. These are part of the write ahead logging/shared memory process and should be removed when the database is closed.

That was the issue with the Kobo firmware that was prone to database corruption in that the USB connection was established before the databases were closed.
DNSB is offline   Reply With Quote