MobileRead Forums - View Single Post

davidfor · 07-05-2017, 08:36 PM

Yes, that's a corrupt database. And it needs to be fixed before doing anything else. There is a small chance that doing a compress on the database will fix things, but I would not expect it to. You need to restore a copy from a recent backup (if you have one), or sign out of the Kobo account on the device and then back in. The latter will remove the existing bad database, create a new empty one and load all the sideloaded books and any purchased books will be downloaded.

What do you mean by "wiped it twice"? Factory resets or just deleting files? If you have done a couple of factory resets and the database was corrupted shortly afterwards, it's either a faulty device or bad practices.

The one way I know to corrupt the database is to unplug from a PC at the wrong time. If you correctly eject it, everything should be OK. The other things I can think where I would expect corruption to happen is if the device is crashing for some reason or restarting the device using the pinhole-reset. Both of these could mean the database isn't saved properly. If it the corruption is happening during normal use with no other unexpected events, then it might be a faulty device.

07-05-2017, 08:36 PM	#2
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	Yes, that's a corrupt database. And it needs to be fixed before doing anything else. There is a small chance that doing a compress on the database will fix things, but I would not expect it to. You need to restore a copy from a recent backup (if you have one), or sign out of the Kobo account on the device and then back in. The latter will remove the existing bad database, create a new empty one and load all the sideloaded books and any purchased books will be downloaded. What do you mean by "wiped it twice"? Factory resets or just deleting files? If you have done a couple of factory resets and the database was corrupted shortly afterwards, it's either a faulty device or bad practices. The one way I know to corrupt the database is to unplug from a PC at the wrong time. If you correctly eject it, everything should be OK. The other things I can think where I would expect corruption to happen is if the device is crashing for some reason or restarting the device using the pinhole-reset. Both of these could mean the database isn't saved properly. If it the corruption is happening during normal use with no other unexpected events, then it might be a faulty device.