View Single Post
Old 03-08-2022, 06:37 AM   #2
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
I am pretty sure that is a side effect of the general issues with firmware 4.31 and the issues with connecting to the device. The issue is that something on the device is not letting the books partition unmount properly. And then all sorts of things happen. In this case, I suspect that when the device remounts the partition, it is mounted read-only. I have had some similar behaviour and was able to telnet in and see how the partition was mounted. As you found rebooting fixed it as the database hadn't been updated.

It's not strictly a calibre issue. The device was in a state where anything that accessed the database would have caused this. And I am not sure if it needed anything to access the database. It might have happened if you just accessed the drive. And if you had the scan-disk prompt from Windows and didn't, that might have been the trigger.
davidfor is offline   Reply With Quote