![]() Notifications, based on CPU, network, disk, battery, weather and other events. Refined menu bar items, dropdowns and other aspects match the new design of macOS 11 Big Sur. Maybe displaying them in columns depends on the logs having a particular format that Console can parse.Weather with current temperature, hourly forecast, weekly overview and so much more. But the reports are simply files in the logs directories, and Console is just displaying them. Note that it is normal for Time Machine to display some errors, such as “failed to remove attribute”.Īre you running as a non-administrator? If so, maybe that’s why you don’t have permission to view the System log.įor the interface questions, on Mojave I don’t have any columns in Reports logs. De-select DAS and CTS unless the problem is related to Time Machine not running when it should.Note that this is relative to timestamp in the next field, so you you want to re-run Mints again, you will need to click the Now button. Howard Oakley at The Eclectic Light Company has been fighting the unified log battle for years, and has several free utilities that can show Time Machine logs, including Consolation 3, Ulbow, and The Time Machine Mechanic, but I think the best one for this purpose is Mints. 10.12 Sierra switched to the “unified log”, where the relevant log messages are buried in a torrent of incomprehensible messages.įor Time Machine, in theory you can craft a Console query that will filter for the Time Machine log messages. The last version of macOS with a usable Console was OS X 10.11 El Capitan. I welcome suggestions, especially “Don’t worry about it.” (It was just under 6 GB last night.) The last backup is consistently reported as Oct 27, which is why I say that the backups are failing to complete. For what it’s worth, the number of GB has been creeping up while Time Machine is running. In my experience, Time Machine often (maybe 40% of the time) will, at the end of a backup, stop reporting progress and just say something like, “Backup up: 6.75 GB” (which is what it says right now), and at least the last four attempts by Time Machine to complete a backup have gone directly to this line. I’m not sure what the Mac’s problem is, but it continues. The Memory Pressure is a level green area that takes up perhaps a fifth of the available area, and the sum of the Memory Used and the Cached Files was less than the Physical Memory (it is now slightly more) and Swap Used is and was 0 bytes. The Memory tab leads me to believe that I do not have a memory problem. If you suspect the memory problem, you can see it happen with the memory tab in Activity Monitor. It seems like I could exclude the System folder from the Time Machine backup and avoid the problem at no cost. But why? If Time Machine did finish its backup, could I use it to restore the System folder? I thought that the System folder was a copy of a sealed volume, and so a backup would be useless anyway. I assume Time Machine is trying to copy the changed System folder. This started immediately after I installed macOS 11.6.1 my last completed backup was just before the installation. Three or four attempts ago, it was at 4.something GB of about 5.9 GB before it stopped.) But Time Machine does seem to be backing up more and more slowly each time it runs. Since I installed macOS 11.6.1 on my MBA M1, Time Machine has repeatedly quit without finishing its backup, although it seems to get a bit further each time. The question is, how to get past this and get Time Machine working again? Or, maybe there’s something wrong in the Spotlight database – SuperDuper was getting stuck yesterday trying to clone those folders in /private, before I updated it to the 3.5 beta which ignores the Spotlight metadata. I’m thinking that when Time Machine is comparing the last backup to the current state of the iMac, there’s too many changes found. IStat menus shows that each time it attempts a backup, the swap memory grows to just short of 50 GB, then backupd gets killed. ![]() (): Service exited due to SIGKILL | sent by kernel_task I can see in the logs that what’s happening is the kernel is killing backupd because it is using too much memory:Ģ1-10-16 14:06:23.436 kernel low swap: killing largest compressed process with pid 1366 (backupd) and size 260 MB The symptom is that it will be in “Preparing Backup…” for a long time, then the backup just quits with no errors shown. Time Machine has stopped working on my iMac running Mojave.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |