MobileRead Forums
Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Software > Calibre > Devices
Reload this Page [Kobo] database disk image is malformed

Notices

Reply
Page 2 of 3 1 2 3
 
Thread Tools Search this Thread
Old 08-21-2021, 07:32 AM   #16
smiley1081
Member
smiley1081 is clearly one to watchsmiley1081 is clearly one to watchsmiley1081 is clearly one to watchsmiley1081 is clearly one to watchsmiley1081 is clearly one to watchsmiley1081 is clearly one to watchsmiley1081 is clearly one to watchsmiley1081 is clearly one to watchsmiley1081 is clearly one to watchsmiley1081 is clearly one to watchsmiley1081 is clearly one to watch
 
Posts: 14
Karma: 10794
Join Date: Jan 2016
Location: Italy
Device: Kobo Glo HD
There was a recent upgrade to my Kobo, and I am getting the error.

Could it be that this is due to the fact the Calibre has not yet reached the same level of the new Kobo version?
smiley1081 is offline   Reply With Quote
Old 08-21-2021, 08:20 AM   #17
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by smiley1081 View Post
There was a recent upgrade to my Kobo, and I am getting the error.

Could it be that this is due to the fact the Calibre has not yet reached the same level of the new Kobo version?
That is definitely not the case. The database on the device has not changed in any significant way for a very long time. And lots of people are not seeing any issues like this. I have outlined this above, and in a lot more detail in the Kobo forum.
davidfor is offline   Reply With Quote
Advert
Old 08-30-2021, 03:08 PM   #18
dem1980fr
Enthusiast
dem1980fr began at the beginning.
 
Posts: 34
Karma: 10
Join Date: Aug 2020
Device: Kobo Libra
I have some errors in the database

Code:
calibre, version 5.26.0
ERREUR : Exception non gérée: <b>CorruptError</b>:CorruptError: database disk image is malformed

calibre 5.26 [64bit]  embedded-python: True is64bit: True
Windows-10-10.0.19041 Windows ('64bit', 'WindowsPE')
('Windows', '10', '10.0.19041')
Python 3.8.5
Windows: ('10', '10.0.19041', '', 'Multiprocessor Free')
Interface language: fr
Successfully initialized third party plugins: Amazon.com Multiple Countries (1, 0, 0) && KePub Output (3, 5, 3) && Kobo Books (1, 8, 2) && Kobo Utilities (2, 14, 1) && KoboTouchExtended (3, 5, 3) && Obok DeDRM (6, 7, 0)
Traceback (most recent call last):
  File "calibre_plugins.koboutilities.action", line 1784, in vacuum_device_database
  File "calibre_plugins.koboutilities.action", line 3754, in _vacuum_device_database
apsw.CorruptError: CorruptError: database disk image is malformed

Code:
Résultat de l'exécution de la commande 'PRAGMA integrity_check' sur la base de données du dispositif Kobo:


*** in database main ***
On tree page 20466 cell 0: invalid page number 20633
On tree page 20466 cell 122: invalid page number 20630
On tree page 20466 cell 121: invalid page number 20628
On tree page 20466 cell 120: invalid page number 20627
On tree page 20466 cell 119: invalid page number 20624
On tree page 20466 cell 118: invalid page number 20623
On tree page 20466 cell 117: invalid page number 20620
On tree page 20466 cell 116: invalid page number 20616
On tree page 20466 cell 115: invalid page number 20614
On tree page 20466 cell 114: invalid page number 20612
On tree page 20466 cell 113: invalid page number 20611
On tree page 20466 cell 112: invalid page number 20608
On tree page 20466 cell 111: invalid page number 20604
On tree page 20466 cell 110: invalid page number 20602
On tree page 20466 cell 109: invalid page number 20598
On tree page 20466 cell 108: invalid page number 20597
On tree page 20466 cell 107: invalid page number 20596
On tree page 20466 cell 106: invalid page number 20590
On tree page 20466 cell 105: invalid page number 20589
On tree page 20466 cell 104: invalid page number 20587
On tree page 20466 cell 103: invalid page number 20584
On tree page 20466 cell 102: invalid page number 20583
On tree page 20466 cell 101: invalid page number 20579
On tree page 20466 cell 100: invalid page number 20574
On tree page 20466 cell 99: invalid page number 20572
On tree page 20466 cell 98: invalid page number 20571
On tree page 20466 cell 97: invalid page number 20568
On tree page 20466 cell 96: invalid page number 20564
On tree page 20466 cell 95: invalid page number 20563
On tree page 20466 cell 94: invalid page number 20560
On tree page 20466 cell 93: invalid page number 20557
On tree page 20466 cell 92: invalid page number 20555
On tree page 20466 cell 91: invalid page number 20552
On tree page 20466 cell 90: invalid page number 20548
On tree page 20466 cell 89: invalid page number 20546
On tree page 20466 cell 88: invalid page number 20545
On tree page 20466 cell 87: invalid page number 20542
On tree page 20466 cell 86: invalid page number 20538
On tree page 20466 cell 85: invalid page number 20536
On tree page 20466 cell 84: invalid page number 20532
On tree page 20466 cell 83: invalid page number 20531
Page 19450: btreeInitPage() returns error code 11
On tree page 19458 cell 2: Rowid 12856 out of order
On tree page 17690 cell 86: 2nd reference to page 19457
On tree page 16277 cell 64: 2nd reference to page 16701
On tree page 5791 cell 2: invalid page number 20551
On tree page 5791 cell 2: Child page depth differs
On tree page 5791 cell 1: Child page depth differs
On tree page 5629 cell 10: invalid page number 20618
On tree page 5629 cell 9: invalid page number 20601
On tree page 5629 cell 8: invalid page number 20586
On tree page 5629 cell 7: invalid page number 20566
On tree page 5629 cell 6: invalid page number 20550
On tree page 5629 cell 5: invalid page number 20535
On tree page 6634 cell 4: invalid page number 20541
On tree page 6634 cell 4: Child page depth differs
On tree page 6634 cell 3: invalid page number 20607
On tree page 5742 cell 2: invalid page number 20621
On tree page 5742 cell 1: invalid page number 20606
On tree page 5742 cell 0: invalid page number 20595
On tree page 6634 cell 2: Child page depth differs
On tree page 4720 cell 1: invalid page number 20610
On tree page 4720 cell 8: invalid page number 20582
On tree page 4720 cell 7: invalid page number 20567
On tree page 4720 cell 6: invalid page number 20554
On tree page 4720 cell 5: invalid page number 20540
On tree page 20521 cell 0: invalid page number 20629
On tree page 20521 cell 78: invalid page number 20626
On tree page 20521 cell 77: invalid page number 20619
On tree page 20521 cell 76: invalid page number 20613
On tree page 20521 cell 75: invalid page number 20605
On tree page 20521 cell 74: invalid page number 20600
On tree page 20521 cell 73: invalid page number 20594
On tree page 20521 cell 72: invalid page number 20588
On tree page 20521 cell 71: invalid page number 20581
On tree page 20521 cell 70: invalid page number 20573
On tree page 20521 cell 69: invalid page number 20565
On tree page 20521 cell 68: invalid page number 20562
On tree page 20521 cell 67: invalid page number 20553
On tree page 20521 cell 66: invalid page number 20547
On tree page 20521 cell 65: invalid page number 20539
On tree page 20521 cell 64: invalid page number 20534
On tree page 7408 cell 6: invalid page number 20527
On tree page 7408 cell 6: Child page depth differs
On tree page 7408 cell 5: Child page depth differs
On tree page 6828 cell 5: 2nd reference to page 20526
On tree page 6828 cell 5: Child page depth differs
On tree page 6828 cell 4: invalid page number 20592
On tree page 5770 cell 3: 2nd reference to page 20525
On tree page 5770 cell 2: invalid page number 20537
On tree page 5770 cell 1: invalid page number 20615
On tree page 5770 cell 0: invalid page number 20631
On tree page 6828 cell 3: Child page depth differs
On tree page 5666 cell 2: invalid page number 20622
On tree page 5666 cell 8: invalid page number 20603
On tree page 5666 cell 7: invalid page number 20591
On tree page 5666 cell 6: invalid page number 20580
On tree page 5666 cell 5: invalid page number 20569
On tree page 5666 cell 4: invalid page number 20556
On tree page 5666 cell 3: invalid page number 20544
dem1980fr is offline   Reply With Quote
Old 08-31-2021, 01:28 AM   #19
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by dem1980fr View Post
I have some errors in the database

Code:
calibre, version 5.26.0
ERREUR : Exception non gérée: <b>CorruptError</b>:CorruptError: database disk image is malformed

calibre 5.26 [64bit]  embedded-python: True is64bit: True
Windows-10-10.0.19041 Windows ('64bit', 'WindowsPE')
('Windows', '10', '10.0.19041')
Python 3.8.5
Windows: ('10', '10.0.19041', '', 'Multiprocessor Free')
Interface language: fr
Successfully initialized third party plugins: Amazon.com Multiple Countries (1, 0, 0) && KePub Output (3, 5, 3) && Kobo Books (1, 8, 2) && Kobo Utilities (2, 14, 1) && KoboTouchExtended (3, 5, 3) && Obok DeDRM (6, 7, 0)
Traceback (most recent call last):
  File "calibre_plugins.koboutilities.action", line 1784, in vacuum_device_database
  File "calibre_plugins.koboutilities.action", line 3754, in _vacuum_device_database
apsw.CorruptError: CorruptError: database disk image is malformed

Code:
Résultat de l'exécution de la commande 'PRAGMA integrity_check' sur la base de données du dispositif Kobo:


*** in database main ***
On tree page 20466 cell 0: invalid page number 20633
On tree page 20466 cell 122: invalid page number 20630
On tree page 20466 cell 121: invalid page number 20628
On tree page 20466 cell 120: invalid page number 20627
On tree page 20466 cell 119: invalid page number 20624
On tree page 20466 cell 118: invalid page number 20623
On tree page 20466 cell 117: invalid page number 20620
On tree page 20466 cell 116: invalid page number 20616
On tree page 20466 cell 115: invalid page number 20614
On tree page 20466 cell 114: invalid page number 20612
On tree page 20466 cell 113: invalid page number 20611
On tree page 20466 cell 112: invalid page number 20608
On tree page 20466 cell 111: invalid page number 20604
On tree page 20466 cell 110: invalid page number 20602
On tree page 20466 cell 109: invalid page number 20598
On tree page 20466 cell 108: invalid page number 20597
On tree page 20466 cell 107: invalid page number 20596
On tree page 20466 cell 106: invalid page number 20590
On tree page 20466 cell 105: invalid page number 20589
On tree page 20466 cell 104: invalid page number 20587
On tree page 20466 cell 103: invalid page number 20584
On tree page 20466 cell 102: invalid page number 20583
On tree page 20466 cell 101: invalid page number 20579
On tree page 20466 cell 100: invalid page number 20574
On tree page 20466 cell 99: invalid page number 20572
On tree page 20466 cell 98: invalid page number 20571
On tree page 20466 cell 97: invalid page number 20568
On tree page 20466 cell 96: invalid page number 20564
On tree page 20466 cell 95: invalid page number 20563
On tree page 20466 cell 94: invalid page number 20560
On tree page 20466 cell 93: invalid page number 20557
On tree page 20466 cell 92: invalid page number 20555
On tree page 20466 cell 91: invalid page number 20552
On tree page 20466 cell 90: invalid page number 20548
On tree page 20466 cell 89: invalid page number 20546
On tree page 20466 cell 88: invalid page number 20545
On tree page 20466 cell 87: invalid page number 20542
On tree page 20466 cell 86: invalid page number 20538
On tree page 20466 cell 85: invalid page number 20536
On tree page 20466 cell 84: invalid page number 20532
On tree page 20466 cell 83: invalid page number 20531
Page 19450: btreeInitPage() returns error code 11
On tree page 19458 cell 2: Rowid 12856 out of order
On tree page 17690 cell 86: 2nd reference to page 19457
On tree page 16277 cell 64: 2nd reference to page 16701
On tree page 5791 cell 2: invalid page number 20551
On tree page 5791 cell 2: Child page depth differs
On tree page 5791 cell 1: Child page depth differs
On tree page 5629 cell 10: invalid page number 20618
On tree page 5629 cell 9: invalid page number 20601
On tree page 5629 cell 8: invalid page number 20586
On tree page 5629 cell 7: invalid page number 20566
On tree page 5629 cell 6: invalid page number 20550
On tree page 5629 cell 5: invalid page number 20535
On tree page 6634 cell 4: invalid page number 20541
On tree page 6634 cell 4: Child page depth differs
On tree page 6634 cell 3: invalid page number 20607
On tree page 5742 cell 2: invalid page number 20621
On tree page 5742 cell 1: invalid page number 20606
On tree page 5742 cell 0: invalid page number 20595
On tree page 6634 cell 2: Child page depth differs
On tree page 4720 cell 1: invalid page number 20610
On tree page 4720 cell 8: invalid page number 20582
On tree page 4720 cell 7: invalid page number 20567
On tree page 4720 cell 6: invalid page number 20554
On tree page 4720 cell 5: invalid page number 20540
On tree page 20521 cell 0: invalid page number 20629
On tree page 20521 cell 78: invalid page number 20626
On tree page 20521 cell 77: invalid page number 20619
On tree page 20521 cell 76: invalid page number 20613
On tree page 20521 cell 75: invalid page number 20605
On tree page 20521 cell 74: invalid page number 20600
On tree page 20521 cell 73: invalid page number 20594
On tree page 20521 cell 72: invalid page number 20588
On tree page 20521 cell 71: invalid page number 20581
On tree page 20521 cell 70: invalid page number 20573
On tree page 20521 cell 69: invalid page number 20565
On tree page 20521 cell 68: invalid page number 20562
On tree page 20521 cell 67: invalid page number 20553
On tree page 20521 cell 66: invalid page number 20547
On tree page 20521 cell 65: invalid page number 20539
On tree page 20521 cell 64: invalid page number 20534
On tree page 7408 cell 6: invalid page number 20527
On tree page 7408 cell 6: Child page depth differs
On tree page 7408 cell 5: Child page depth differs
On tree page 6828 cell 5: 2nd reference to page 20526
On tree page 6828 cell 5: Child page depth differs
On tree page 6828 cell 4: invalid page number 20592
On tree page 5770 cell 3: 2nd reference to page 20525
On tree page 5770 cell 2: invalid page number 20537
On tree page 5770 cell 1: invalid page number 20615
On tree page 5770 cell 0: invalid page number 20631
On tree page 6828 cell 3: Child page depth differs
On tree page 5666 cell 2: invalid page number 20622
On tree page 5666 cell 8: invalid page number 20603
On tree page 5666 cell 7: invalid page number 20591
On tree page 5666 cell 6: invalid page number 20580
On tree page 5666 cell 5: invalid page number 20569
On tree page 5666 cell 4: invalid page number 20556
On tree page 5666 cell 3: invalid page number 20544
It looks like the corruption in the database is to much for the VACUUM to fix. Which means either restoring a backup, or signing out of the device and back in to create a new database.

Are you reading comics in CBZ or CBR format? A problem has been discovered with this that can mean the database will be corrupted after attempting to use it in calibre or the Kobo desktop application, or for that matter, anything that tries to update the database. This seems to explain the problems some people are having with corrupt databases.
davidfor is offline   Reply With Quote
Old 09-02-2021, 02:19 PM   #20
dem1980fr
Enthusiast
dem1980fr began at the beginning.
 
Posts: 34
Karma: 10
Join Date: Aug 2020
Device: Kobo Libra
yes i am reading cbz.
For now, i have restored my device and i have no errors.

There is a tool to create a "valid" cbz so it could not corrupt the database ?
dem1980fr is offline   Reply With Quote
Advert
Old 09-02-2021, 03:09 PM   #21
PeterT
Grand Sorcerer
PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.
 
Posts: 13,532
Karma: 78910202
Join Date: Nov 2007
Location: Toronto
Device: Libra H2O, Libra Colour
It has nothing to do with the structure of the cbz; rather it has to do with a bug on the reader itself where some files are not being closed and/or processes not being terminated when a USB connection is made


Sent from my Pixel 4a using Tapatalk
PeterT is offline   Reply With Quote
Old 09-02-2021, 09:22 PM   #22
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
@dem1980fr: As PeterT said, it is a bug on the device. Hopefully Kobo will fix it soon. It has apparently been a problem for a long time, but, it was only recently that we connected the dots. I don't know if the fact we haven't realised this before is because not many people read CBZ/CBRs on Kobo devices. Or if there is something else happening. It is possible is that it might only happen if the last book read was a comic. Of if the device was connected within a certain amount of time of the comic being closed.

As a workaround, you can convert the CBZ to epub, kepub or PDF. None of these formats suffer from this problem.
davidfor is offline   Reply With Quote
Old 11-19-2021, 09:17 AM   #23
GreatSyxsuke
Enthusiast
GreatSyxsuke doesn't litterGreatSyxsuke doesn't litter
 
Posts: 25
Karma: 156
Join Date: Feb 2016
Device: Kobo Libra 2
I picked up a Libra 2 about 2 weeks ago and love it……except for the fact that pretty much daily I’ve had the database corrupt after connecting to Calibre. It doesn’t happen every time though, which makes it hard to track down a culprit.

At first I thought it was using CBT or CBZ files as noted before so I converted them to EPUB. I also thought maybe the eject button in Calibre was not ejecting it properly so I switched to using the actual OS to do so. Since that didn’t fix things, perhaps it was the USB-C to USB-C cable I was using so I switched to only using the one that came in the box. None of this has made a big difference, it seems. In fact, I’ve already had to log out and do a reset twice today since even replacing the file with the backed up database didn’t seem to fix it.

I have noticed that the sign it has happened seems to be when the Kobo is ejected, it reboots rather than doing the Importing Content screen. Is it possible the Libra 2 still isn’t fully supported by Calibre?
Last edited by GreatSyxsuke; 11-19-2021 at 09:55 AM.
GreatSyxsuke is offline   Reply With Quote
Old 11-19-2021, 09:37 AM   #24
ownedbycats
Custom User Title
ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.
 
ownedbycats's Avatar
 
Posts: 10,982
Karma: 75337983
Join Date: Oct 2018
Location: Canada
Device: Kobo Libra H2O, formerly Aura HD
Personally, I'd suspect that the SD card in your Libra could be faulty out of the box, though take this with a grain of salt until others chime in. Still I'd suggest checking your warranty.
Last edited by ownedbycats; 11-19-2021 at 09:41 AM.
ownedbycats is offline   Reply With Quote
Old 11-19-2021, 10:11 AM   #25
GreatSyxsuke
Enthusiast
GreatSyxsuke doesn't litterGreatSyxsuke doesn't litter
 
Posts: 25
Karma: 156
Join Date: Feb 2016
Device: Kobo Libra 2
Quote:
Originally Posted by ownedbycats View Post
Personally, I'd suspect that the SD card in your Libra could be faulty out of the box, though take this with a grain of salt until others chime in. Still I'd suggest checking your warranty.
Thank you for the idea. I looked into it and I have plenty of time to return or exchange it if the warranty doesn't cover it so if that's the way I have to go, I know I'm covered. Hopefully that's not the issue though.
GreatSyxsuke is offline   Reply With Quote
Old 11-19-2021, 11:02 AM   #26
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,064
Karma: 60358908
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Be sure you wait for the Safe to remove (USB cable) message. USB transfers can be buffered by the OS and not truly completed when you click Eject. (I've see up to 30 seconds before Calibre even drops 'OnDevice' )
Also, Kobos have a' Importing' screen. I always wait until My Books screen shows
theducks is offline   Reply With Quote
Old 11-19-2021, 11:10 AM   #27
GreatSyxsuke
Enthusiast
GreatSyxsuke doesn't litterGreatSyxsuke doesn't litter
 
Posts: 25
Karma: 156
Join Date: Feb 2016
Device: Kobo Libra 2
Quote:
Originally Posted by theducks View Post
Be sure you wait for the Safe to remove (USB cable) message. USB transfers can be buffered by the OS and not truly completed when you click Eject. (I've see up to 30 seconds before Calibre even drops 'OnDevice' )
Also, Kobos have a' Importing' screen. I always wait until My Books screen shows
That's good to know, although I'm on a MacBook so there's no "Safe to Remove" message that I'm aware of haha. I have seen the "Importing..." screen but the last time I had my Libra connected, it didn't show up at all and just went blank before doing the start up dots.

I just did a manual reset since I already lost my stats many times so I'll wait until the My Books screen shows up before disconnecting the cable and see if that was the issue. Thanks!
GreatSyxsuke is offline   Reply With Quote
Old 11-19-2021, 11:29 AM   #28
PeterT
Grand Sorcerer
PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.
 
Posts: 13,532
Karma: 78910202
Join Date: Nov 2007
Location: Toronto
Device: Libra H2O, Libra Colour
Quote:
Originally Posted by theducks View Post
Also, Kobos have a' Importing' screen. I always wait until My Books screen shows
Actually the Importing screen doesn't necessarily show up on ejecting the device (either via calibre or the OS). While my Kobos alway show that screen when ejected from Windows, they never do when ejected from a Chrome book.

Sent from my Pixel 4a using Tapatalk
PeterT is offline   Reply With Quote
Old 11-19-2021, 11:44 AM   #29
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,064
Karma: 60358908
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by PeterT View Post
Actually the Importing screen doesn't necessarily show up on ejecting the device (either via calibre or the OS). While my Kobos alway show that screen when ejected from Windows, they never do when ejected from a Chrome book.

Sent from my Pixel 4a using Tapatalk
Mine only shows when ADDING books.
It does not show on the second (series metadata update) connect
theducks is offline   Reply With Quote
Old 11-19-2021, 12:27 PM   #30
ownedbycats
Custom User Title
ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.ownedbycats ought to be getting tired of karma fortunes by now.
 
ownedbycats's Avatar
 
Posts: 10,982
Karma: 75337983
Join Date: Oct 2018
Location: Canada
Device: Kobo Libra H2O, formerly Aura HD
Quote:
Originally Posted by theducks View Post
Mine only shows when ADDING books.
It does not show on the second (series metadata update) connect
Also, if you use "do not treat replacements as new books" option in the driver settings, it won't do the import process for re-sent books.
ownedbycats is offline   Reply With Quote
Reply
Page 2 of 3 1 2 3

« Previous Thread | Next Thread »

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Error in Kobo Glo: database disk image is malformed Carpidor Devices 2 08-07-2015 07:17 AM
Calibre + Kobo Touch error message : database disk image is malformed Bernard75 Devices 1 04-07-2012 03:46 PM
Kobo error: database disk image is malformed RSaunders Devices 7 07-28-2011 09:52 PM
Error communicating with device(Kobo Wireless)/database disk image is malformed cotej1977 Devices 2 04-26-2011 09:34 PM
Error communicating with device(Kobo Wireless)/database disk image is malformed cotej1977 Kobo Reader 1 04-24-2011 08:14 AM


All times are GMT -4. The time now is 09:58 AM.

Contact Us - FAQ - Guidelines - Privacy - Top

MobileRead.com is a privately owned, operated and funded community.