Database is corrupt - a question

[LordP]

I just had this thing happen again, thankfully DNSBs trick of rebooting the Clara BW cleared the problem.

My question is this: Is this problem accelerating?

I don't remember having this issue over and over with the older Kobos. It seems to be a prevalent thing these days.

[pdurrant]

Originally Posted by LordP

I just had this thing happen again, thankfully DNSBs trick of rebooting the Clara BW cleared the problem.

My question is this: Is this problem accelerating?

I don't remember having this issue over and over with the older Kobos. It seems to be a prevalent thing these days.

There are two causes of database corruption

(1) a bug in the software (which might be Kobo software, or any other software that writes to the database)
(2) disconnecting the Kobo from a computer before it's been unmounted properly

(2) is by far the most common cause.

[LordP]

I completely agree with you pdurrant, but I can promise you that I have always waited for the Kobo home screen to appear AND refresh after importing before unplugging from my computer.

Why? Because I burned myself that way once - and once was enough.

I still think this is happening a bit too often.

[John F]

Originally Posted by LordP

I just had this thing happen again, thankfully DNSBs trick of rebooting the Clara BW cleared the problem.

...

I thought DNSB's trick was to reboot before connecting to a PC to prevent database corruption?

[JSWolf]

Originally Posted by LordP

I just had this thing happen again, thankfully DNSBs trick of rebooting the Clara BW cleared the problem.

My question is this: Is this problem accelerating?

I don't remember having this issue over and over with the older Kobos. It seems to be a prevalent thing these days.

Forget rebooting. There's another solution that may work. Roll back the firmware to the previous version that didn't seen to have this issue.

[DNSB]

Originally Posted by LordP

I just had this thing happen again, thankfully DNSBs trick of rebooting the Clara BW cleared the problem.

Originally Posted by John F

I thought DNSB's trick was to reboot before connecting to a PC to prevent database corruption?

That is correct. When my Sage was on the iffy firmware version, I would reboot to ensure the database was properly closed before connecting to my computer.

There have been several reports about database corruption on the Kobo Libra Colour and Clara Colour though I hadn't seen any before this report for the Clara BW. Those have been reported to Kobo.

[DNSB]

Originally Posted by JSWolf

Forget rebooting. There's another solution that may work. Roll back the firmware to the previous version that didn't seen to have this issue.

There aren't many firmware revisions for a Clara BW to roll back to.

[JSWolf]

Originally Posted by DNSB

There aren't many firmware revisions for a Clara BW to roll back to.

Thanks for that bit of info.

[PeterT]

I will admit to encountering database corruption this last week on a KLC. I had connected the device to my Chromebook and done a copy of the contents to the Chromebook prior to using OBOK on the copied data (so NOT accessing the Kibo). I then ejected the device, did a WiFi sync and reconnected to the KLC. At this point the database was corrupted.

Sent from my Pixel 7a using Tapatalk

[PeterT]

Originally Posted by PeterT

I will admit to encountering database corruption this last week on a KLC. I had connected the device to my Chromebook and done a copy of the contents to the Chromebook prior to using OBOK on the copied data (so NOT accessing the Kibo). I then ejected the device, did a WiFi sync and reconnected to the KLC. At this point the database was corrupted.

Sent from my Pixel 7a using Tapatalk

In hindsight I think the device might still have been importing data after the wireless sync. This raises the question though of how to tell this has completed; unlike the post sideloading sync there is no status message displayed.

Sent from my Pixel 7a using Tapatalk

[meeera]

Originally Posted by PeterT

In hindsight I think the device might still have been importing data after the wireless sync. This raises the question though of how to tell this has completed; unlike the post sideloading sync there is no status message displayed.

Unless I'm missing something here, I just tap on the Sync symbol and wait until "Sync complete" is displayed.

[PeterT]

Yes, but I'm not at all sure that the scan / importation of data into the database has completed at that point. Yes; the transfer of dasta from the Kobo site HAS completed but there is still an additional stage on the device itself.

[LordP]

Originally Posted by DNSB

That is correct. When my Sage was on the iffy firmware version, I would reboot to ensure the database was properly closed before connecting to my computer.

There have been several reports about database corruption on the Kobo Libra Colour and Clara Colour though I hadn't seen any before this report for the Clara BW. Those have been reported to Kobo.

Well, yes and no. I connected to the PC first, which is how I found out the database was corrupt. Then I rebooted and reconnected to the PC.

[JSWolf]

Originally Posted by LordP

I just had this thing happen again, thankfully DNSBs trick of rebooting the Clara BW cleared the problem.

My question is this: Is this problem accelerating?

I don't remember having this issue over and over with the older Kobos. It seems to be a prevalent thing these days.

There is another option to maybe solve the problem.

You can install the previous firmware and DO NOT SYNC so you don't get the same firmware you have now.

[LordP]

Originally Posted by JSWolf

There is another option to maybe solve the problem.

You can install the previous firmware and DO NOT SYNC so you don't get the same firmware you have now.

I have done that in the past and may do it again.

I have another stupid question, or two, though.

In my scenario, I plugged the device in, and the database was declared corrupt, I unplugged it, rebooted, and then it came up as OK.

So, was the database corrupted or not?
If it was corrupted, does the device rebuild the database when it reboots?

I very rarely reboot, almost never.

Also, to clarify what I do when detaching the Clara from my PC: I disconnect through Calibre, I also check that it's disconnected from the USB in the system tray. I wait for the device to turn the screen on, fully lit, and then go through the process of importing and back to the home screen, again fully lit - ONLY THEN do I unplug it.

If that method corrupts the database, well, then I guess I'm screwed because I can't think of anything else I could possibly do.