Thread: database disk image malformed
View Single Post
Old 03-06-2024, 02:05 PM   #6
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: 29,877
Karma: 55267620
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 smiley1081 View Post
Thanks!

Given the times one gets the "database disk image malformed" error this answer should probably be pinned.
It should be rare.
Always connect WITH the HOME screen showing (never with a book open)
Always EJECT
WAIT before doing anything else with the device. It may not be instant before SAFE to eject
Then WAIT for the device to finish processing (happens when adding), again. It takes time for the Eject to be recognized, then the check for new to complete.
FINALLY, you can pull the plug

FWIW other than some bad Kobo FW, I have had this happen 1 time between my Aura2 and my Libra2. Both get LOTS of use.
theducks is offline   Reply With Quote