View Single Post
Old 07-22-2021, 11:27 PM   #9
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,053
Karma: 169810634
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Skydog View Post
Well, add me to @franklekens. The identical problem just happened to me too. I've had five Kobo readers and never have I had this occur. Since it's new, I was in the process of sideloading additional books and did not yet have a backup. I hope this isn't the beginning of a buggy new device!
It would appear that all the posts about database corruption in the last while have been connected to using a Kobo Elipsa.

For what it's worth, my current experience with an Elipsa is a customer who is looking at them as replacements for their aging Sony DPT eNote devices. After sideloading the corporate content and "safely" ejecting the Elipsa, they have been shutting the connected computer down before unplugging the USB cable. Not exactly the speediest process but so far they have not seen any database corruption.
DNSB is offline   Reply With Quote