Firmware 4.31.19086

[Calenorn]

Originally Posted by ownedbycats

Thankfully, in 4.31's case, its not a problem wiht the database, but with the filesystem dismounting before it should.

And what triggers it to do that? That’s what I’d like to know.

[ownedbycats]

Originally Posted by Calenorn

And what triggers it to do that? That’s what I’d like to know.

Take a look here: https://www.mobileread.com/forums/sh...91#post4198591

Mostly it just seems to result in Windows bugging the user with scan & fix prompts, but if the unmount happens at just the right moment while the sqlite file is in use you might get a corrupt database. Some users have mentioned it happening when connecting while the Kobo's still generating covers, for example.

My instances were all after importing new books and then immediately re-connnecting to fetch subtitles from Calibre. Waiting a few minutes seemed to help.

[compurandom]

Originally Posted by ownedbycats

Thankfully, in 4.31's case, its not a problem wiht the database, but with the filesystem dismounting before it should. So restoring the backup should work.

The filesystem issues cause the database to get corrupted. The corruption accumulates and the device can continue working with a corrupted database, which then gets backed up one or more times... so you've missed my point.

[davidfor]

Originally Posted by compurandom

I wish that was 100% true, but I've found that the database corruption can be subtle and not immediately detected, and the most recent backup may also be corrupt.

The backup runs a full check after taking a copy of the database file. If there are any problems with the database, you will see an error and "CORRUPT" will be added to the file name.

Putting the database back on the device can result in a corrupt database. As you don't have control of everything involved what is happening, something could happen to corrupt the database after it is replaced. I have not decided on the best way to do it. I power off, but, whether it is better to do it as soon as the device is disconnected or after the home screen is displayed, I'm not sure.

[compurandom]

Originally Posted by davidfor

The backup runs a full check after taking a copy of the database file. If there are any problems with the database, you will see an error and "CORRUPT" will be added to the file name.

That's good to know, but I don't think it is enough.

I think sometimes the database corruption leaves the data in the database wrong, but the database itself is OK. The usual symptom I see is that overdrive stops working and expires all my books. However, I've seen stranger things like phantom books that can't be deleted. I don't know if sqlite has an internal dirty flag or something that would help.

[davidfor]

Originally Posted by compurandom

That's good to know, but I don't think it is enough.

I think sometimes the database corruption leaves the data in the database wrong, but the database itself is OK. The usual symptom I see is that overdrive stops working and expires all my books. However, I've seen stranger things like phantom books that can't be deleted. I don't know if sqlite has an internal dirty flag or something that would help.

That's a completely different issue. That is data integrity rather than the low-level database integrity. The check that is being done is a low level test of whether the database file is constructed properly. There is no attempt to validate that the data in the database is consistent. And honestly, there is no practical way to do it. Or at least in any reasonable amount of time.

If there are data issues, then it is usually a because of a bug in the application. Probably something not writing the all of the data. Problems like what you mention could be signs of corrupt databases. Or they could be that the data memory does not match what is in the database. In that case, when the attempt is made to update the database, it might fail and what happens then depends on how errors are handled. Kobo appears to ignore these sort of errors to and keep working using the in memory data. Which is why we see problems with losing data after a restart.

[JSWolf]

Originally Posted by davidfor

The backup runs a full check after taking a copy of the database file. If there are any problems with the database, you will see an error and "CORRUPT" will be added to the file name.

Putting the database back on the device can result in a corrupt database. As you don't have control of everything involved what is happening, something could happen to corrupt the database after it is replaced. I have not decided on the best way to do it. I power off, but, whether it is better to do it as soon as the device is disconnected or after the home screen is displayed, I'm not sure.

When i copied the contents of the H2O to the Libra 2, I just did it. I was at the home screen of the Libra 2 with 4.30 installed. And it did work with no problems.

[Colonel Cathcart]

I'm curious how many of you who have experienced problems with this firmware reported it directly to Kobo.
How about starting a poll with the answers:
1. I didn't experience any problems so far.
2. I'm experiencing some issue(s) and wrote about it here.
3. I'm experiencing some issue(s) and reported it to Kobo.

Something along those lines.
Might be interesting to see the results.

[John F]

Originally Posted by Colonel Cathcart

I'm curious how many of you who have experienced problems with this firmware reported it directly to Kobo.
How about starting a poll with the answers:
1. I didn't experience any problems so far.
2. I'm experiencing some issue(s) and wrote about it here.
3. I'm experiencing some issue(s) and reported it to Kobo.

Something along those lines.
Might be interesting to see the results.

How about 2 more options:

4. I didn't upgrade
5. I am experiencing some issue(s) and wrote about it here and reported it to Kobo.

[compurandom]

Originally Posted by Colonel Cathcart

I'm curious how many of you who have experienced problems with this firmware reported it directly to Kobo.

6. I reported the problem and they told me to log out and log back in and/or reset firmware and did not report the bug to developers because there is a known fix.

[Quoth]

7. I went back to an earlier version.
8. Even 4.30.x seems broken on Elipsa (BT on only turns on WiFi), so considering going to back earlier as BT did work on original version when bought Jan 2022.

[Odyssee]

For me: 7. I went back to an earlier version.
The Page Turn Buttons on my Sage were not very responsive, had to push them more than once with the 4.31 firmware. Under 4.30 it seems a lot better.

[Colonel Cathcart]

I'm trying to make the choices as mutually exclusive as possible.
This place is a watering hole. It's very accessible, you get quick responses. This makes it so attractive I'm wondering how many contact the vendor. The one with the actual power to investigate issues thoroughly and squash them.
That's the focus of my suggestion. I guess there are plenty of other interesting polls hiding here. Maybe make this polling thing standard with each firmware release?

[ZodWallop]

Originally Posted by ZodWallop

My collections are still not quite right.

At this point, I've removed and re-added all of my books to the Clara. It did repopulate my collections. But I have a few where I removed the tag in Calibre, but it persists on the Clara.

This appears to be wrong. There were a few pesky books in Calibre that did have tags when I thought they didn't.

Collections appear to be working again as expected.

[JSWolf]

For the poll, I would only go with options 1-3, and 5. The rest skew the numbers for the intent of the poll.