MobileRead Forums - View Single Post - Database is corrupt

DNSB · 01-25-2025, 05:32 PM

If it is similar to the last database corruption issue, the problem was that the databases were not properly closed before the USB connection was established. In a file explorer, you would see files called KoboReader.sqlite-wal, KoboReader.sqlite-shm, BookReader.sqlite-wal BookReader.sqlite-shm (not necessarily both pairs but even one pair indicates that database was not properly closed) in the .kobo directory.

My workaround was to force a reboot using NickelMenu to ensure the database was closed before the USB connection.

What I also found was the if I got the database corrupted message and immediately ejected, the database will be closed which also merges the -wal and -shm file so the next connection will not show a corrupt database. If any attempt to write to the database is made, this will leave the database in a corrupt state. For me using Windows, this meant closing calibre immediately and then ejecting by right-clicking on the Kobo drive in File Explorer and then on Eject.

I suspect this is why the OP saw the now I'm corrupted, now I'm not corrupted behaviour.

01-25-2025, 05:32 PM	#29
DNSB Bibliophagist Posts: 47,260 Karma: 171291590 Join Date: Jul 2010 Location: Vancouver Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos	If it is similar to the last database corruption issue, the problem was that the databases were not properly closed before the USB connection was established. In a file explorer, you would see files called KoboReader.sqlite-wal, KoboReader.sqlite-shm, BookReader.sqlite-wal BookReader.sqlite-shm (not necessarily both pairs but even one pair indicates that database was not properly closed) in the .kobo directory. My workaround was to force a reboot using NickelMenu to ensure the database was closed before the USB connection. What I also found was the if I got the database corrupted message and immediately ejected, the database will be closed which also merges the -wal and -shm file so the next connection will not show a corrupt database. If any attempt to write to the database is made, this will leave the database in a corrupt state. For me using Windows, this meant closing calibre immediately and then ejecting by right-clicking on the Kobo drive in File Explorer and then on Eject. I suspect this is why the OP saw the now I'm corrupted, now I'm not corrupted behaviour. Last edited by DNSB; 01-25-2025 at 05:35 PM.