Smart Utility can also do regular drive scans and send you email if it detects a problem, which has saved my bacon more than once over the years. #Timemachineeditor full#It can do the full SMART communication with drive, show you what errors the drive is producing, and run short and long tests. If you don’t have it, Volitans Smart Utility has a full featured 30 day demo. That SMART Verified thingie? It has nothing to do with the health of the drive, it only means that the drive controller is still alive. Slow downs are the most common, but not the only thing. Since drive errors are no longer routinely communicated to operating systems, all sorts of weird stuff can start to happen when a drive starts to fail. Or maybe there is way to set up a script to forcibly terminate the local snapshot processes after a TM backup is complete.)ĭo you have a hard drive or a SSD? If it’s a spinny drive, check it out for problems. Or perhaps there is some way to make the local snapshot processes non-executable. Perhaps there is something in a launchd plist you could disable. (Of course, if you can happily live without local snapshots, you could google around and/or muck around to see if there is some way to disable the local snapshot processes. Well, maybe Apple will get around to you in 10.12 or 10.13… And if it does work, the TimeMachineEditor workaround would actually work around the bug. Again, probably won’t work, but it’s quick enough to be worth a try. #Timemachineeditor manual#And that would explain why the TimeMachineEditor workaround fails, since after it does the backup, even though TM is disabled, the local snapshot processes stick around.Īnd it probably won’t work, but you should at least try turning off TM, *rebooting* to make sure the local snapshot processes are quit, and *then* doing a manual backup. If turning off TM, rebooting, and not backing up for a bit to troubleshoot *does* end the local snapshot nightmare, it just means that those processes never properly quit after a backup is done. If you’re still getting the mess even with it turned off, I guess the local snapshot functionality is enabled even with TM disabled. You could try simply turning off TM, rebooting, and not backing up for a couple of hours to troubleshoot. I find these entries to be interesting.ġ2/7/15 18:32:47.000 kernel: Sandbox: mtmfs(552) System Policy: deny(1) forbidden-rootless-xattrġ2/7/15 18:32:47.156 mtmfs: could not set attributes on destination file descriptor: Operation not permitted: Operation not permittedġ2/7/15 19:33:33.810 : () Unknown key for Boolean: ForceEnableHackġ2/7/15 19:33:33.810 : () This service is defined to be constantly running and is inherently inefficient. Update: I found the following in system logs. I reinstalled El Capitan, and nothing changed. I’ve contacted AppleCare, and spent a lot of time on this, sending them logs and other data, and I’m waiting to hear back. So it’s clearly Time Machine that’s killing my battery. When I check Activity Monitor, and look at Energy, the app listed as having the highest impact is Time Machine, way above Safari which is the second. It should only do this when it can’t access your Time Machine disk it then copies those snapshots the next time the Time Machine disk is available. But I’m only using the MacBook at my home office, so it’s on the network where my Time Machine backup device is located, and it shouldn’t make local snapshots. These two processes are related to Time Machine, and have something to do with creating local snapshots. Here’s a screenshot from iStat Menus when that happens: One thing I notice is that two processes, mtmd and mtmfs, pop up frequently, using about 100% of CPU (of a core) and do so for a while. I’ve been using it a lot in the past week, and I’ve noticed that I’m getting perhaps 6 hours of battery life, without using a lot of apps. I use it for testing, for taking screenshots, and for working outside my office from time to time. My MacBook is my second computer, and I don’t use it much.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |