01-03-2024, 08:28 PM | #31 | |
Resident Curmudgeon
Posts: 74,037
Karma: 129333114
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
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. |
|
01-03-2024, 10:02 PM | #32 | |
Bibliophagist
Posts: 35,498
Karma: 145557716
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Forma, Clara HD, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
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.
Quote:
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 |
|
Advert | |
|
01-07-2024, 06:28 PM | #33 | |
Addict
Posts: 248
Karma: 1135030
Join Date: Nov 2010
Location: West Yorkshire
Device: Kobo Forma
|
Quote:
Having tried all sorts, I continue to have this problem on a regular basis. |
|
01-10-2024, 02:32 AM | #34 |
Addict
Posts: 248
Karma: 1135030
Join Date: Nov 2010
Location: West Yorkshire
Device: Kobo Forma
|
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. Last edited by leaston; 01-10-2024 at 03:20 AM. |
01-10-2024, 05:25 AM | #35 |
the rook, bossing Never.
Posts: 11,169
Karma: 85874891
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper11
|
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. Last edited by Quoth; 01-10-2024 at 05:30 AM. |
Advert | |
|
01-10-2024, 09:21 AM | #36 | |
Addict
Posts: 248
Karma: 1135030
Join Date: Nov 2010
Location: West Yorkshire
Device: Kobo Forma
|
Quote:
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. |
|
01-10-2024, 11:20 AM | #37 | |
the rook, bossing Never.
Posts: 11,169
Karma: 85874891
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper11
|
Yours was without a USB connection.
Quote:
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. Last edited by Quoth; 01-10-2024 at 11:24 AM. |
|
01-10-2024, 02:30 PM | #38 | |
Bibliophagist
Posts: 35,498
Karma: 145557716
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Forma, Clara HD, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
Quote:
This does not appear to be from operator error but simply the cards having a limited life. |
|
01-10-2024, 04:16 PM | #39 | |
Addict
Posts: 248
Karma: 1135030
Join Date: Nov 2010
Location: West Yorkshire
Device: Kobo Forma
|
Quote:
|
|
01-10-2024, 04:21 PM | #40 | |
Addict
Posts: 248
Karma: 1135030
Join Date: Nov 2010
Location: West Yorkshire
Device: Kobo Forma
|
Quote:
|
|
01-10-2024, 04:24 PM | #41 |
Custom User Title
Posts: 8,644
Karma: 61234567
Join Date: Oct 2018
Location: Canada
Device: Kobo Libra H2O, formerly Aura HD
|
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. Last edited by ownedbycats; 01-10-2024 at 04:28 PM. |
01-10-2024, 04:53 PM | #42 |
Bibliophagist
Posts: 35,498
Karma: 145557716
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Forma, Clara HD, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
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.
|
01-11-2024, 03:01 PM | #43 |
Addict
Posts: 248
Karma: 1135030
Join Date: Nov 2010
Location: West Yorkshire
Device: Kobo Forma
|
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. |
01-11-2024, 06:01 PM | #44 |
Wizard
Posts: 1,026
Karma: 11500112
Join Date: Sep 2022
Device: Kobo Libra 2
|
As long as you're sideloading and don't need to sync, you can just stay on 4.34 forever and be happy.
|
02-14-2024, 06:56 AM | #45 | |
Grand Sorcerer
Posts: 5,018
Karma: 18018738
Join Date: Nov 2009
Location: UK
Device: Kobo Forma, Libra2, Clara 2e, Kindle PW SE & Kindle 2022
|
Quote:
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Clara Error: database disk image is malformed | Terisa de morgan | Kobo Reader | 7 | 11-09-2020 07:41 AM |
Strange malformed database error | itimpi | Library Management | 2 | 12-19-2013 09:00 AM |
ERROR - database disk image malformed | Joy1977 | Calibre | 2 | 05-11-2012 11:28 PM |
Kobo error: database disk image is malformed | RSaunders | Devices | 7 | 07-28-2011 09:52 PM |
Error: malformed database schema (books_insert_trg) | cbatalla | Calibre | 4 | 05-08-2010 01:02 PM |