**** BEGIN LOGGING AT Sat Sep 23 03:00:03 2017 Sep 23 16:07:25 I know it was yesterday, but I wouldn't use my device for paying on the go. Also I would walk or cycle over a taxi. Sep 23 20:25:28 Problem: I have fsck auto-running every time I switch on N900. On top of that, after MyDocs is finally mounted, tracker takes up 10% CPU re-indexing it, apparently. Sep 23 20:26:01 last time i remember it's because fsck cant fix it in automode Sep 23 20:26:06 so you have to fix it yourself Sep 23 20:26:10 Question: how do I fix MyDocs so that I don't have fsck running on every start-up? Sep 23 20:26:32 i dont remember, is it exported via usb? Sep 23 20:26:36 /me doesn't remember exact flags-options needed for fsck Sep 23 20:26:39 if yes, you can fsck from windoze Sep 23 20:26:48 (or linux) Sep 23 20:27:09 1) no usb; 2) almost no windoze. Sep 23 20:27:37 1) Aka broken microUSB port. Sep 23 20:28:03 ~fsck Sep 23 20:28:03 No devices specified to be checked! Sep 23 20:28:27 ~dosfsck Sep 23 20:28:38 ~listkeys dosfsck Sep 23 20:28:39 Factoid search of 'dosfsck' by key returned no results. Sep 23 20:28:59 ~fsck.vfat -a /dev/mmcblk0p1 Sep 23 20:29:10 dont forget to umount it first Sep 23 20:29:16 That's what auto-fsck does. Sep 23 20:29:29 Yes, umount /dev/mmcblk0p1 Sep 23 20:30:01 ~test Sep 23 20:30:01 test is, like, not funny Sep 23 20:30:38 Okay, infobot is alive. i was worried after its silence in response to fsck line. Sep 23 20:31:16 What other flags are needed? Sep 23 20:31:25 try with -a first Sep 23 20:31:50 it will ask you for things that needs confirmation Sep 23 20:32:02 (or backup important data and run with -y) Sep 23 20:32:18 I already tried -aw and -taw. Runs way too quickly, gives no errors or warnings, and still fsck happens after reboot. Sep 23 20:33:04 another issue is that you turn it off and eject battery too quickly Sep 23 20:33:15 so it doesnt umount things correctly Sep 23 20:33:38 I have a looping led pattern on shutdown to prevent too fast battery ejection. Sep 23 20:34:40 Besides, the latest reboot was without battery ejection - just in honour of manually done fsck (because I don't know other way to mount MyDocs back). Sep 23 20:42:41 Okay, will shotdown, change battery, see if fsck -a is happening, if yes then wait till it is finished and umount MyDocs and run fsck -ftvw on MyDocs. Sep 23 20:43:26 Shutdown * Sep 23 20:52:04 Okay, at least I took the opportunity to move several photographs and a movie out of shadows while MyDocs is being fsck-ed. Aka, consequence of using camera while MyDocs isn't mounted, yet. Sep 23 20:53:01 By the way, why does auto-capitalisation of letters only work after MyDocs is mounted? Sep 23 20:53:39 Same for symbols on-screen assistant for hardware keyboard. Sep 23 20:55:01 why does osso-addressbook take up 20 percent of CPU? are the images for contacts stored on MyDocs? Sep 23 20:56:35 no, it functions fine even as fsck is running. Sep 23 20:59:12 MyDocs is mounted, trackerd eats CPU. Let's umount it... Sep 23 21:00:40 Congratulations, cannot umount /home/user/MyDocs: Device or resource busy Sep 23 21:01:42 Tracker-indexer, is that you? Sep 23 21:03:49 By the way, fsck 1.42.5 is five years old, by now. Sep 23 21:04:55 Fsck -ftvw starts up fsck.vfat -f Sep 23 21:05:22 If it doesn't help, I will be running fsck.vfat -ftvw, next time. Sep 23 21:06:57 Because this lack of verbosity is annoying. Sep 23 21:16:32 Fsck -ftvw finished. Fsck.vfat -ftrvw starting. Sep 23 22:00:49 Fsck.vfat -ftrvw done, no errors or warnings. Sep 23 22:02:03 Any idea how to mount MyDocs without rebooting? Or is rebooting safer? **** ENDING LOGGING AT Sun Sep 24 03:00:00 2017