Thread: Kobo Start Menu 09
View Single Post
Old 03-14-2018, 03:31 AM   #163
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 Elaxon View Post
I reset my Kobo H20 Aura and deleted all the books and such to transfer everything back in epub format. One thing I noticed after applying everything is when I transfer the sqlite database made by calibre utilities it kept bootlooping and eventually forcing me to factory reset.

But I managed to restore the read states with Calibre but it seems deleting the books when the sqlite database refers to them will cause a bootloop. Not sure if I could do anything differently.
To be completely successful when restoring the database from a backup (I assume that is what you meant by "database made by calibre utilities"), the books need to be back in the same place as before. Otherwise, the first thing the device will do is compare what is in the database with what is on the disk and start removing the missing books from the database and adding the ones that aren't in the database. And you should shutdown the device as soon as you can after restoring the database and disconnecting the device.

I have done this enough times to know it works if I take care. And I have messed it up enough to now that I need to pay attention to what I am doing. Also, I don't use KSM and don't know if it would affect this, but, I wouldn't expect so if you are using a recent version of KSM.

My guess would be that if a large number of books couldn't be found, the process doing the cleanup might have been seen by sickel as hung and sickel triggered a reboot. I wouldn't have expected a continuous reboot, unless it hadn't actually removed any books from the database before the reboot happened or possibly if the database was corrupted.
davidfor is offline   Reply With Quote