Forma Database Malformed error

[JSWolf]

Originally Posted by DNSB

It does not matter whether I read ePub, kepub, PDF or CBZ. I still see the remnant files. I tested by opening multiple books in different formats and it seems to make no difference.

Maybe this is an issue with the Sage.

I have an idea if it will work. Can you create a NickelMenu command that will only reboot if either of those files are present meaning something is not properly closed?

That would save even more time and less rebooting.

[DNSB]

Originally Posted by JSWolf

Maybe this is an issue with the Sage.

I can get the same issues on a Clara HD, Libra 2 and Elipsa 2E. The Elipsa and the Sage are the most likely to glitch.

Originally Posted by JSWolf

I have an idea if it will work. Can you create a NickelMenu command that will only reboot if either of those files are present meaning something is not properly closed?

That would save even more time and less rebooting.

For me, the time saved would not be worthwhile considering how fast my Sage reboots.

If you are able to supply a NickelMenu item that would do something like the following pseudo-code, feel free to do so:

If exist (.kobo/*.sqlite-wal) then reboot else USB connect

[leaston]

Originally Posted by Josieb1

I'm suddenly seeing the Database Malformed error on my Kobo Forma when trying to add new books via Calibre.

I have had the same problem for the last few weeks. I can fix it by reparing the account in the Forma settings menu, but despite getting all the books back, they all lose their reading status/progress.

Having tried all sorts, I continue to have this problem on a regular basis.

[leaston]

Ok, having messed around with the Forma, still on the latest firmware, I have found a really odd one.

I opened the cover and went back to the home screen from the book I was reading. I then powered off the Forma. There was a notification on the screen saying 'powered off' along with the cover of the book I'm currently reading. Powered it back on and the database was corrupted.

So, at least on mine, closing the book you're reading and rebooting in order to ensure no database files are left open does not work. I didn't even get to plug in the USB cable because rebooting seemed to kill the database.

I'm baffled and sick of it now. Time to downgrade the firmware. Not happy with Kobo!

EDIT: I repaired the account via the menu and rebooted...database still broken. So, repairing doesn't fix it now either. That's also new.

EDIT 2: I downloaded and installed firmware 4.34. That worked and the Forma restarted successfully - still only showing the books after the corruption happened with the later firmware.
I connected to Calibre and:
CorruptError: database disk image is malformed
Traceback (most recent call last):
File "calibre\gui2\device.py", line 104, in run
File "calibre\gui2\device.py", line 558, in _books
File "calibre\devices\kobo\driver.py", line 2028, in books
File "C:\t\t\apsw-42s16m2x\src\cursor.c", line 240, in resetcursor
apsw.CorruptError: CorruptError: database disk image is malformed

So, I'm back to square one. I'll try a factory reset and firmware 4.34 next. If that doesn't work, I have no clue what to do next.

EDIT 3: Well, it all seems ok now. Here's what I ended up doing...
Downgraded to Firmware 4.34.
Performed a factory reset via the Forma menu.
Once it restarted, went through the setup and activated the Forma via the Kobo site.
Turned off wifi to prevent it from trying to upgrade the firmware back to 4.38.
Connected to Calibre, sideloaded a few books.
Used Calibre to remove the Forma from the PC connection.
And, this is where things change...
On firmware 4.38 I noticed that the screen of the Kobo still showed the computer icons even after using the Calibre menu in the Windows Taskbar to disconnect the Forma.
On firmware 4.34 it drops me back the the Home screen on the Forma within a few seconds of using Calibre to disconnect! Hmmmm. Still doesn't explain the corruption after a reboot without using Calibre at all.

Anyway, so far, having reconnected and disconnected from the PC using Calibre, along with rebooting a couple of times, it seems to be working as it should on the old firmware. Fingers crossed.

I must admit this has soured me to Kobo. To break their own ereader with a firmware update and leave us trying to fix it ourselves is absolutely unforgiveable.

[Quoth]

You may have had Flash storage corruption. Eventually the bad blocks would be remapped with re-writing the files by various resets/upgrades. Other people have only had the issue when connecting USB, and not everyone. Windows updates also may have affected some USB users.
Some people on the latest firmware have had no issues at all, but do always close the current ebook before connecting cable and on eject wait for bar progress to end (before unplugging cable) and screen displaying ebooks to flash (database update complete, obvious if filter set to unread as list changes) before reconnecting.

[leaston]

Originally Posted by Quoth

You may have had Flash storage corruption. Eventually the bad blocks would be remapped with re-writing the files by various resets/upgrades. Other people have only had the issue when connecting USB, and not everyone. Windows updates also may have affected some USB users.
Some people on the latest firmware have had no issues at all, but do always close the current ebook before connecting cable and on eject wait for bar progress to end (before unplugging cable) and screen displaying ebooks to flash (database update complete, obvious if filter set to unread as list changes) before reconnecting.

If this were an isolated incident, I'd probably agree that perhaps the storage became corrupted through my doing things in the 'wrong' order when disconnecting the device or some other reason related to my actions. Maybe.

However, I'm far from alone in seeing this error, repeatedly - and it doesn't seem to be isolated to the Forma, which still suggests a software/firmware issue.

As I said before, my behaviour around using the reader hasn't changed at all in years and switching to a previous firmware version seems, for now, to have resolved the problem. The only thing different about my Forma between it behaving normally and beginning to display the error is the firmware update. That it happened last night without even being plugged in means Calibre and my PC aren't to blame either.

[Quoth]

Yours was without a USB connection.

That it happened last night without even being plugged in means Calibre and my PC aren't to blame either.

So Flash storage failed by itself.
The other people are discussing USB transfers, where some have no issues and others can avoid it with a reboot. Definitely SQLight files open.

Your symptoms and solution are different.

Flash storage does suffer from blocks fading even when not in use. An update re-writing files will cure that and absolutely bad blocks will be hidden.

[DNSB]

Originally Posted by leaston

If this were an isolated incident, I'd probably agree that perhaps the storage became corrupted through my doing things in the 'wrong' order when disconnecting the device or some other reason related to my actions. Maybe.

This is not going to help with your Forma but quite a few of the people to whom I have sent links to Kobo firmware images have reported that trying to reuse the original µSD card shows that it has uncorrectable errors. One person reported that after copying the image to his original µSD card, his Glo would boot and work normally however installing a firmware update caused his Glo to error again. Trying a replacement µSD card allowed him to revive and update his Glo without error. The SD Association's formatter utility reported multiple errors when attempting to format the original card.

This does not appear to be from operator error but simply the cards having a limited life.

[leaston]

Originally Posted by Quoth

Yours was without a USB connection.

So Flash storage failed by itself.
The other people are discussing USB transfers, where some have no issues and others can avoid it with a reboot. Definitely SQLight files open.

Your symptoms and solution are different.

Flash storage does suffer from blocks fading even when not in use. An update re-writing files will cure that and absolutely bad blocks will be hidden.

I wonder after reading your post if it's one causing the other. Mine did begin with a USB transfer and happened around 50% of the time when disconnecting from the PC. Then, last night the behaviour changed to happening upon reboot.

[leaston]

Originally Posted by DNSB

This is not going to help with your Forma but quite a few of the people to whom I have sent links to Kobo firmware images have reported that trying to reuse the original µSD card shows that it has uncorrectable errors. One person reported that after copying the image to his original µSD card, his Glo would boot and work normally however installing a firmware update caused his Glo to error again. Trying a replacement µSD card allowed him to revive and update his Glo without error. The SD Association's formatter utility reported multiple errors when attempting to format the original card.

This does not appear to be from operator error but simply the cards having a limited life.

I remember one of my old readers having a card inside (Kobo Glo maybe). If it's the storage on the Forma that's failing then I guess it is time to replace it.

[ownedbycats]

I retired my Aura HD due to failing internal storage. It started out with seemingly random glitches, like reading position occasionally failing to save or sideloaded books failing to load and needing to be re-sent. Then the database corruptions started happening, first very rarely but then more frequently as time went on.

It was 8 or 9 years old at this time I think. I could've probably figured out how to swap out the internal storage (though my Parkinson's makes my fine motor coordination not so great) but I wanted to upgrade to a model with page-turn buttons.

[DNSB]

Originally Posted by leaston

I remember one of my old readers having a card inside (Kobo Glo maybe). If it's the storage on the Forma that's failing then I guess it is time to replace it.

Sadly true. Unless you happen to have a surface mount rework station handy, the cost of replacing the eMMC storage chip would exceed the cost of a replacement ereader by a good chunk. OTOH, you might want to hang in there for a few months. Kobo has a couple of FCC approval requests in from Oct and Dec 2023.

[leaston]

The Forma hasn't corrupted since I downgraded the firmware. Coincidence or fix? Who knows I hope it hangs on long enough for either Kobo to release something decent with their impending new models, or I cave and return to Kindle.

Haha, David my soldering skills with a normal iron are passable on a good day. I dread to think of the mess I'd make with surface mount kit!

It would be even better if there were other reasonably priced options in the UK. The competition is scarce here though and I don't fancy paying import duty and other fees for something from abroad.

[Aleron Ives]

As long as you're sideloading and don't need to sync, you can just stay on 4.34 forever and be happy.

[Josieb1]

Originally Posted by ownedbycats

I retired my Aura HD due to failing internal storage. It started out with seemingly random glitches, like reading position occasionally failing to save or sideloaded books failing to load and needing to be re-sent. Then the database corruptions started happening, first very rarely but then more frequently as time went on.

It was 8 or 9 years old at this time I think. I could've probably figured out how to swap out the internal storage (though my Parkinson's makes my fine motor coordination not so great) but I wanted to upgrade to a model with page-turn buttons.

I know its been a while since I had the malformed problem but its happened twice now since then. I'm beginning to think i'll lose my Forma because of this .Its only about three years old but I know the device has been around longer than that.