Quote:
Originally Posted by jbaumann
The next experiment could be to install fmon directly. Any recommendations about which package to use? And should I uninstall KSM first or is it enough to have it configured as never to run?
This way I could find out whether fmon works without problems. Earlier experiments showed already that KSM leads to problems even with fmon disabled.
|
I think if it is certain that no instance of fmon was running, when the corruption occurred, then there is no need to deal further with fmon.
So the issue seems to occur when (1) KSM is active and (2) nickel has to deal with a newly modified database and (3) at the same time with newly added books. I do not see what exactly is the problem with this setting. But maybe we can change it a little, and see what happens:
- Maybe you could start with a new booted device (so that nickel was not yet running)
- select enable usb id like nickel.sh
- add new books with calibre
- eject, disable and disconnect
- start nickel
- make nickel process the new books by opening simulate_usb_connection.png (see this post for the details); or connect and disconnect really.
I am curious whether this makes a difference.
The issue mentioned by Peter is also alarming.