Quote:
Originally Posted by davidfor
Another thing to try is to not eject from within the applications, either calibre or the Kobo desktop. Close these and wait a couple of minutes. That should make sure nothing that you are doing trying to update, and it should let any caches flush as well. I don't know the MAC, but, Windows has, or at least had, an option for "fast eject" or something like that. Turning it on, meant that writes to removable media were immediate and not cached.
|
Good response. Thank you. There IS a lot new with the Elipsa compared to other Kobo eReaders, and since I'm using the same software and computer with my Clara as I do my Elipsa, and the Clara soldiers on without incident, I'm thinking the Elipsa has an issue. I am crossing my fingers that it's something they can fix in firmware, unlike the backlighting issues with the Forma that people just had to live with. I wish I could isolate what is triggering this issue, but I'll keep a watchful eye. Restoring my Elipsa so often is a pain in the back.
However, I'll follow your suggestion and quit the apps before ejecting the Elipsa. If Time Machine, Spotlight, Kobo Desktop, Terminal, and Calibre are not accessing the mounted Elipsa, I'll look into how to spot what other process could be poking around in the Elipsa's SD Card before ejecting. Still, the Mac is VERY stubborn about not allowing disks to be ejected if a process is running that is using the drive. I'm thinking there is something going wrong when the Elipsa recognizes it is no longer connected and runs through a check that detects changes before opening to Home. Next time the corruption happens, I'll try restoring one SQLite database at a time to see which one is the problem.
Kobo should be paying us. LOL
