Glad to hear it worked for you. I don't own an Apple Silicon Mac, so I'm not much help to that crowd since things behave differently on that platform than Intel. At least they can.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Resolved Time machine experiencing multiple issues on Monterey (my personal issue resolved)
- Thread starter MacinMan
- Start date
- Sort by reaction score
Actually, for the better part of the day, I've been enjoying playing around with Mojave on a late 2013, 13" MBP, and getting it set up as a legacy system for 32-bit support (if I need it.)
I had put Monterey on it via OpenCore Legacy Patcher, and it was working great. I just decided since I had tested it and it worked, I'd rather go back to a legacy OS. By Nature, I keep up to date for security and features, but I like older tech too. I just checked my Time Machine drive, as I had set it and forgot it, and it's still keeping up without trouble.
I had put Monterey on it via OpenCore Legacy Patcher, and it was working great. I just decided since I had tested it and it worked, I'd rather go back to a legacy OS. By Nature, I keep up to date for security and features, but I like older tech too. I just checked my Time Machine drive, as I had set it and forgot it, and it's still keeping up without trouble.
Just to follow this up, I’ve now run a few incremental backups on 2 separate TM disks and the rates and completion times are now back to what they were pre-Monterey. I am using an Intel iMac and I reformatted my TM disks on Monterey.
Same here (Intel iMac as well) Also wanted to note that storage capacity seems to be better managed as well. e.g. The drive isn't filling up as fast this time around from TM backups.
One thing I wanted to mention, I also flushed the drive several times before reusing it formatting it 2 to 3 times to make sure it was fully wiped. One thing I noticed, is on it initial reformat, it was quite slow, as I repeated it each time, it got faster. I don't have a lot of information, or experience on this, but I've heard/read that Disk Utility can have some bugs when it comes to formatting with certain filesystems. I've made it a point at some point to learn the command line diskutil. I just never need to use it that often, so I've forgotten about it. I like gparted from Linux, but as far as I know, there isn't a native macOS version.
Surely this must be a bug with macOS Monterey 12.0.1 running on Apple Silicone? It's working perfectly fine from my Intel X86 MacBook Pro, but ever since macOS Monterey it has never worked on my Apple Silicone Mac mini.
I even tried to restore my Mac mini using the 12.0.1 IPSW through Apple Configurator and setting it up completely fresh. No Rosetta2 enable or anything. Still getting:
2021-11-11 15:08:40 Failed to acquire device lock assertion for /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Anduril-Macmini/2021-11-11-150305/Macintosh HD - Data/Users/ramguy/Library/Containers/com.apple.findmy.FindMyWidgetPeople/Data/Library error: Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument"
2021-11-11 15:08:40 Failed to acquire device lock assertion for /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Anduril-Macmini/2021-11-11-150305/Macintosh HD - Data/Users/ramguy/Library/Containers/com.apple.findmy.FindMyWidgetPeople/Data/Documents error: Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument"
2021-11-11 15:08:40 Failed to acquire device lock assertion for /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Anduril-Macmini/2021-11-11-150305/Macintosh HD - Data/Users/ramguy/Library/Containers/com.apple.findmy.FindMyWidgetPeople/Data/tmp error: Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument"
2021-11-11 15:08:46 Failed to acquire device lock assertion for /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Anduril-Macmini/2021-11-11-150305/Macintosh HD - Data/Users/ramguy/Library/Containers/com.apple.findmy.FindMyWidgetIntentsPeople/Data/Library error: Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument"
2021-11-11 15:08:46 Failed to acquire device lock assertion for /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Anduril-Macmini/2021-11-11-150305/Macintosh HD - Data/Users/ramguy/Library/Containers/com.apple.findmy.FindMyWidgetIntentsPeople/Data/Documents error: Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument"
2021-11-11 15:08:46 Failed to acquire device lock assertion for /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Anduril-Macmini/2021-11-11-150305/Macintosh HD - Data/Users/ramguy/Library/Containers/com.apple.findmy.FindMyWidgetIntentsPeople/Data/tmp error: Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument"
2021-11-11 15:08:47 Failed to acquire device lock assertion for /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Anduril-Macmini/2021-11-11-150305/Macintosh HD - Data/Users/ramguy/Library/Containers/com.apple.findmy.FindMyWidgetIntentsItems/Data/Library error: Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument"
2021-11-11 15:08:47 Failed to acquire device lock assertion for /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Anduril-Macmini/2021-11-11-150305/Macintosh HD - Data/Users/ramguy/Library/Containers/com.apple.findmy.FindMyWidgetIntentsItems/Data/Documents error: Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument"
2021-11-11 15:08:47 Failed to acquire device lock assertion for /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Anduril-Macmini/2021-11-11-150305/Macintosh HD - Data/Users/ramguy/Library/Containers/com.apple.findmy.FindMyWidgetIntentsItems/Data/tmp error: Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument"
Using a 30-day trial of Carbon Copy Cloner and is hoping Apple will have this fixed by the time my trial runs out. Could always consider purchasing Carbon Copy Cloner but so far it's extremely slow compared to Apple Time Machine Backups which is annoying.
I even tried to restore my Mac mini using the 12.0.1 IPSW through Apple Configurator and setting it up completely fresh. No Rosetta2 enable or anything. Still getting:
2021-11-11 15:08:40 Failed to acquire device lock assertion for /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Anduril-Macmini/2021-11-11-150305/Macintosh HD - Data/Users/ramguy/Library/Containers/com.apple.findmy.FindMyWidgetPeople/Data/Library error: Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument"
2021-11-11 15:08:40 Failed to acquire device lock assertion for /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Anduril-Macmini/2021-11-11-150305/Macintosh HD - Data/Users/ramguy/Library/Containers/com.apple.findmy.FindMyWidgetPeople/Data/Documents error: Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument"
2021-11-11 15:08:40 Failed to acquire device lock assertion for /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Anduril-Macmini/2021-11-11-150305/Macintosh HD - Data/Users/ramguy/Library/Containers/com.apple.findmy.FindMyWidgetPeople/Data/tmp error: Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument"
2021-11-11 15:08:46 Failed to acquire device lock assertion for /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Anduril-Macmini/2021-11-11-150305/Macintosh HD - Data/Users/ramguy/Library/Containers/com.apple.findmy.FindMyWidgetIntentsPeople/Data/Library error: Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument"
2021-11-11 15:08:46 Failed to acquire device lock assertion for /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Anduril-Macmini/2021-11-11-150305/Macintosh HD - Data/Users/ramguy/Library/Containers/com.apple.findmy.FindMyWidgetIntentsPeople/Data/Documents error: Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument"
2021-11-11 15:08:46 Failed to acquire device lock assertion for /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Anduril-Macmini/2021-11-11-150305/Macintosh HD - Data/Users/ramguy/Library/Containers/com.apple.findmy.FindMyWidgetIntentsPeople/Data/tmp error: Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument"
2021-11-11 15:08:47 Failed to acquire device lock assertion for /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Anduril-Macmini/2021-11-11-150305/Macintosh HD - Data/Users/ramguy/Library/Containers/com.apple.findmy.FindMyWidgetIntentsItems/Data/Library error: Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument"
2021-11-11 15:08:47 Failed to acquire device lock assertion for /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Anduril-Macmini/2021-11-11-150305/Macintosh HD - Data/Users/ramguy/Library/Containers/com.apple.findmy.FindMyWidgetIntentsItems/Data/Documents error: Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument"
2021-11-11 15:08:47 Failed to acquire device lock assertion for /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Anduril-Macmini/2021-11-11-150305/Macintosh HD - Data/Users/ramguy/Library/Containers/com.apple.findmy.FindMyWidgetIntentsItems/Data/tmp error: Error Domain=NSPOSIXErrorDomain Code=22 "Invalid argument"
Using a 30-day trial of Carbon Copy Cloner and is hoping Apple will have this fixed by the time my trial runs out. Could always consider purchasing Carbon Copy Cloner but so far it's extremely slow compared to Apple Time Machine Backups which is annoying.
Surprised to hear that your CCC is slow. Mine's been faster than TM but I am copying to an APFS external SSD, via USBc.
Still no joy with TM at the moment. CCC has been a life saver. And it works a treat with Migration Assistant for setup.
Still no joy with TM at the moment. CCC has been a life saver. And it works a treat with Migration Assistant for setup.
Maybe the same bug / condition affecting your Time Machine Backup is also affecting CCC in your circumstances. Many of those tools rely on the same core technologies of the OS. SuperDuper also is free to use for what you might want to try. See if you also experience slowdowns with that as well.
I went back and re-read what I had wrote, and went back to your original post. All I was saying is there have been known bugs / changes on Apple Silicon Macs when it comes to third party backup utilities working as expected, and now that more than one person with an Apple Silicon Mac is reporting issues of varying degrees, I was simply saying that it sounds to me that the same bug, or set of bugs that has been around for a while is now affecting Time machine.
I'm with you though, on the Intel side of things working as expected. I can't speak for Apple Silicon as I don't own one of those Macs.
So glad I found this thread here. Never had this problem with Time Machine backups before, but have been unable to complete a backup of my new 14" M1 Max MacBook Pro. Will wait for a solution from Apple, hopefully with the next macOS Monterey build.
It's important that as many users as possible is reporting these issues through the feedback-app on macOS so it gains traction and goes higher on the list of issues on macOS Monterey. The feedback-app is easy to use, you just have to give some pointers to what is going on and the app will collect debug information and make sure it gets uploaded for you.
Hi All,
I heard back from Apple support today. They told me that they have news from the engineers and will ring tomorrow. Will keep you posted.
I heard back from Apple support today. They told me that they have news from the engineers and will ring tomorrow. Will keep you posted.
So hi all let's summarize this topic as I've got the same problem (across all my devices: M1 MBA, M1 MacMini, Intel 27'' imac i5), i can confirm the following:
based on this i have come to the following conclusion, while consulting with an Apple Netherlands rep:
a user security eval triggers an internal though abnormal macos security process/policy, locking out certain system functions, including but not limited to backups with TimeMachine, Apple Pay, Touch ID, App Store confirm with TouchID, Watch Unlock etc.
let me explain:
when using certain software (EX. Rogue Amoeba AirFoil etc), docks, DAC's or other tools and even chargers a signed kernel extension may necessarily be installed on the mac which requires lowering macos security policy to Reduced Security to get the kernel extensions to run at boot/login and allow the developers to update them, while not everyone in this thread may have those installed, this seems to be the main causer of these headaches especially on M1-Series macs..
Somewhere in this process macos is conflicting with itself, resulting in the loss of or partial loss of off backup functionality, disabled apple pay on macs and other security restrictions in the user space of macos, as listed above.
Now, I've discovered in my testing that there are 2 main triggers for these lockouts:
If you believe it's none of the above, please share your experience as the bug may be even more pernicious and have multiple if not more root causes.
So then, onto my situation, I was frequently having to return to macOS Recovery to change the security policy back and forth, sometime this resulted in time machine and apple pay to get working again other times not.
Now, what machines do i have: I currently write this on my M1 MacBook Air running the non beta 12.0.1 of monterey.
My macMini still runs the last version of Big Sur, my iMac is on monterey non beta as mba above.
imac and macmini backup to a time-capsule where the imac only fails some backups as of the update to monterey, while the macmini refuses to complete a backup if i purposefully trigger the process by installing a software or hardware with a kernel extension necessitating some round-trips to macos recovery to flip the setting, then backups start again.
(on these macs i didn't run any beta this time around)
but now my mba m1, it seems so far to be the one affected the worst, on this device i've run all betas of monterey, up until the final release of monterey, then switched dev beta off. (i'm currently planning to put 12.1 beta on to see if that fixes things)
during the summer beta phase, this m1 mba experienced these issues the heaviest and also intermittently and seemingly randomly, sometime resulting in no backups at all for a week or more, before i even discovered it when looking at the date of last backup in sys preferences. all the while, the menu bar icon did change and indicate a backup progress every so often during that week, as macos normaly does its automated tm backups, but of course failing to complete the backup each time, before i actually discovered it. had i had critical files on this mba, i surely would have lost a few of them.
So..
As of today, timemachine is again refusing to complete backups, my last backup is from 00:54 at midgnight today.
it starts the process of copying files, sometime i even see a new folder appear on the drives, sometime with an .interrupted on the extension, other times, no apparent action takes place on the timemachine volume, other than system preferences and the menu bar item both showing a backup to be in progress.
and the only apparent change to this m1 mba was connecting a new seagate external drive to format it.
That is all. But apparently enough to interfere with both time machine and apple pay again, as both are now refusing to work as they're supposed to, with apple pay in syspref having a message of "card not available as this mac's security settings have changed'.
In any case, flipping full security back on in macos recovery, immediately restores the stored cards and apple pay becomes available again, but then of course, my kernel extensions are disabled such as those for my dac, dock and other hard/software.
to conclude: this bug if you can call it a bug has a complex root cause if not multiple causes and also multiple consequences.
Reading:
eclecticlight.co
- problem appears on both Intel and Silicon macs (M1 to Max) though Apple Silicon macs seems to be affected the worst.
- underlying bug or parts thereof also present in last 3 Big Sur releases.
- formatting of the drives does not matter*
- message about a mac being locked therefor backup is unable to finish, while computer is actually unlocked and in active use**
- problem may appear/disappear intermittently on affected macs.
based on this i have come to the following conclusion, while consulting with an Apple Netherlands rep:
a user security eval triggers an internal though abnormal macos security process/policy, locking out certain system functions, including but not limited to backups with TimeMachine, Apple Pay, Touch ID, App Store confirm with TouchID, Watch Unlock etc.
let me explain:
when using certain software (EX. Rogue Amoeba AirFoil etc), docks, DAC's or other tools and even chargers a signed kernel extension may necessarily be installed on the mac which requires lowering macos security policy to Reduced Security to get the kernel extensions to run at boot/login and allow the developers to update them, while not everyone in this thread may have those installed, this seems to be the main causer of these headaches especially on M1-Series macs..
Somewhere in this process macos is conflicting with itself, resulting in the loss of or partial loss of off backup functionality, disabled apple pay on macs and other security restrictions in the user space of macos, as listed above.
Now, I've discovered in my testing that there are 2 main triggers for these lockouts:
- you may have third party kernel extensions or pseudo-ones*** on your system without knowing it, for example if you've ever used a high watt charger for your mac, installed certain gaming software, or otherwise used software which acts as a virtual drive, disc or audio device****, like the software from rogue amoeba mentioned above, as those install hooks into macos which require the reduced security policy for them to load either as a traditional kernel extensions or pseudo-extension, which aren't actually loaded but still need to be installed.
- recently connected new hardware such as external drives or other devices and/or certain software installations.
If you believe it's none of the above, please share your experience as the bug may be even more pernicious and have multiple if not more root causes.
So then, onto my situation, I was frequently having to return to macOS Recovery to change the security policy back and forth, sometime this resulted in time machine and apple pay to get working again other times not.
Now, what machines do i have: I currently write this on my M1 MacBook Air running the non beta 12.0.1 of monterey.
My macMini still runs the last version of Big Sur, my iMac is on monterey non beta as mba above.
imac and macmini backup to a time-capsule where the imac only fails some backups as of the update to monterey, while the macmini refuses to complete a backup if i purposefully trigger the process by installing a software or hardware with a kernel extension necessitating some round-trips to macos recovery to flip the setting, then backups start again.
(on these macs i didn't run any beta this time around)
but now my mba m1, it seems so far to be the one affected the worst, on this device i've run all betas of monterey, up until the final release of monterey, then switched dev beta off. (i'm currently planning to put 12.1 beta on to see if that fixes things)
during the summer beta phase, this m1 mba experienced these issues the heaviest and also intermittently and seemingly randomly, sometime resulting in no backups at all for a week or more, before i even discovered it when looking at the date of last backup in sys preferences. all the while, the menu bar icon did change and indicate a backup progress every so often during that week, as macos normaly does its automated tm backups, but of course failing to complete the backup each time, before i actually discovered it. had i had critical files on this mba, i surely would have lost a few of them.
So..
As of today, timemachine is again refusing to complete backups, my last backup is from 00:54 at midgnight today.
it starts the process of copying files, sometime i even see a new folder appear on the drives, sometime with an .interrupted on the extension, other times, no apparent action takes place on the timemachine volume, other than system preferences and the menu bar item both showing a backup to be in progress.
and the only apparent change to this m1 mba was connecting a new seagate external drive to format it.
That is all. But apparently enough to interfere with both time machine and apple pay again, as both are now refusing to work as they're supposed to, with apple pay in syspref having a message of "card not available as this mac's security settings have changed'.
In any case, flipping full security back on in macos recovery, immediately restores the stored cards and apple pay becomes available again, but then of course, my kernel extensions are disabled such as those for my dac, dock and other hard/software.
to conclude: this bug if you can call it a bug has a complex root cause if not multiple causes and also multiple consequences.
- * time capsule is formatted as HFS+, M1 MBA backups to a local thunderbolt 3 drive enclosure when plugged in^, and those are in APFS, as those only started their duty of timemachine for the M1 MBA since i got it, and Big Sur formaated them to APFS without me even having the choice of something else
- **earlier in the thread a few of you also reported this message too, this likely is the same security eval bug I explained above, and I directly checked apple pay when the time machine pref-pane gave me this specific error (some time last week), and yes, apple pay was disabled as well, a reboot to macos recovery and a change in security policy again fixed both things, while leaving my extensions disabled for that time, which eventually fixed it self when i again restored the Reduced Security setting. (until today {see above}, both time machine and apple pay were working fine in that mode on my mba m1 again)
- ***what I call pseudo extensions are those that are installed by say your dock, raid enclosure (both hw/sw ex. softraid by owc), or thunderbolt docks/hubs like those from CalDigit or virtual devices for specific video and audio software which do emulation or capturing, you can check them through system profiler when going to about this mac, then software > extensions. notice they are most likely not actually loaded by macos when you're logged in, but exist in a semi loaded state, and really only require to be installed for the software such as the Caldigit dock ejection utility or raid enclosures (like those from owc or others) to function.
- ****for example software from rogue amoeba installs the ACE component to hook into coreaudiod, which to macos acts like a kernel extension requiring the lower security setting, but isn't actually a typical kernel extension which loads when you login, the software of this company only requires it to be authenticated by the system and approved, they use the kernel extension method to accomplish this. which normally doesn't effect macos, unless there is a bug underlying in the security routine of macos which we now experience with monterey and on M-Series macs in particular.
Reading:
Extensions are moving away from the kernel
Management of kernel extensions has changed significantly in Big Sur and later. This overview for users contrasts kexts with user-level extensions which are replacing them.
eclecticlight.co
Last edited:
Hi, thanks for your feedback. When I initially reported the issue, it was simply a speed issue. (not failure) Also, in my case, I don't have a Mac that's recently enough that uses Apple Pay, or the security features the T2 and newer offer. I have Audio Hijack, and Sound Siphon, and VMware Fusion, Toast, etc as far as third party apps that load any kind of extensions. To my knowledge, none of these have ever caused any issues for me. However, thank you for bringing this observation to the thread. Maybe since I don't have a T2 based Intel Mac, none of this extra security info applies to my particular situation. For me anyway, Time machine has been functioning as normal. I try to only use the security that I need for a safe environment. I try not to overdo it because sometimes I feel Apple overdoes it, especially when it comes to people who know what they are doing vs someone who is an average user and needs the extra help.So hi all let's summarize this topic as I've got the same problem (across all my devices: M1 MBA, M1 MacMini, Intel 27'' imac i5), i can confirm the following:
- problem appears on both Intel and Silicon macs (M1 to Max) though Apple Silicon macs seems to be affected the worst.
- underlying bug or parts thereof also present in last 3 Big Sur releases.
- formatting of the drives does not matter*
- message about a mac being locked therefor backup is unable to finish, while computer is actually unlocked and in active use**
- problem may appear/disappear intermittently on affected macs.
based on this i have come to the following conclusion, while consulting with an Apple Netherlands rep:
a user security eval triggers an internal though abnormal macos security process/policy, locking out certain system functions, including but not limited to backups with TimeMachine, Apple Pay, Touch ID, App Store confirm with TouchID, Watch Unlock etc.
let me explain:
when using certain software (EX. Rogue Amoeba AirFoil etc), docks, DAC's or other tools and even chargers a signed kernel extension may necessarily be installed on the mac which requires lowering macos security policy to Reduced Security to get the kernel extensions to run at boot/login and allow the developers to update them, while not everyone in this thread may have those installed, this seems to be the main causer of these headaches especially on M1-Series macs..
Somewhere in this process macos is conflicting with itself, resulting in the loss of or partial loss of off backup functionality, disabled apple pay on macs and other security restrictions in the user space of macos, as listed above.
Now, I've discovered in my testing that there are 2 main triggers for these lockouts:
- you may have third party kernel extensions or pseudo-ones*** on your system without knowing it, for example if you've ever used a high watt charger for your mac, installed certain gaming software, or otherwise used software which acts as a virtual drive, disc or audio device****, like the software from rogue amoeba mentioned above, as those install hooks into macos which require the reduced security policy for them to load either as a traditional kernel extensions or pseudo-extension, which aren't actually loaded but still need to be installed.
- recently connected new hardware such as external drives or other devices and/or certain software installations.
If you believe it's none of the above, please share your experience as the bug may be even more pernicious and have multiple if not more root causes.
So then, onto my situation, I was frequently having to return to macOS Recovery to change the security policy back and forth, sometime this resulted in time machine and apple pay to get working again other times not.
Now, what machines do i have: I currently write this on my M1 MacBook Air running the non beta 12.0.1 of monterey.
My macMini still runs the last version of Big Sur, my iMac is on monterey non beta as mba above.
imac and macmini backup to a time-capsule where the imac only fails some backups as of the update to monterey, while the macmini refuses to complete a backup if i purposefully trigger the process by installing a software or hardware with a kernel extension necessitating some round-trips to macos recovery to flip the setting, then backups start again.
(on these macs i didn't run any beta this time around)
but now my mba m1, it seems so far to be the one affected the worst, on this device i've run all betas of monterey, up until the final release of monterey, then switched dev beta off. (i'm currently planning to put 12.1 beta on to see if that fixes things)
during the summer beta phase, this m1 mba experienced these issues the heaviest and also intermittently and seemingly randomly, sometime resulting in no backups at all for a week or more, before i even discovered it when looking at the date of last backup in sys preferences. all the while, the menu bar icon did change and indicate a backup progress every so often during that week, as macos normaly does its automated tm backups, but of course failing to complete the backup each time, before i actually discovered it. had i had critical files on this mba, i surely would have lost a few of them.
So..
As of today, timemachine is again refusing to complete backups, my last backup is from 00:54 at midgnight today.
it starts the process of copying files, sometime i even see a new folder appear on the drives, sometime with an .interrupted on the extension, other times, no apparent action takes place on the timemachine volume, other than system preferences and the menu bar item both showing a backup to be in progress.
and the only apparent change to this m1 mba was connecting a new seagate external drive to format it.
That is all. But apparently enough to interfere with both time machine and apple pay again, as both are now refusing to work as they're supposed to, with apple pay in syspref having a message of "card not available as this mac's security settings have changed'.
In any case, flipping full security back on in macos recovery, immediately restores the stored cards and apple pay becomes available again, but then of course, my kernel extensions are disabled such as those for my dac, dock and other hard/software.
to conclude: this bug if you can call it a bug has a complex root cause if not multiple causes and also multiple consequences.
only good news is, apple is likely already working on a fix for monterey and as far as the methods these software and hardware companies use to hook into macos for their functionality: they are on their way out and will need to be replaced by another method, as apple is moving away from allowing any kernel extensions.
- * time capsule is formatted as HFS+, M1 MBA backups to a local thunderbolt 3 drive enclosure when plugged in^, and those are in APFS, as those only started their duty of timemachine for the M1 MBA since i got it, and Big Sur formaated them to APFS without me even having the choice of something else
- **earlier in the thread a few of you also reported this message too, this likely is the same security eval bug I explained above, and I directly checked apple pay when the time machine pref-pane gave me this specific error (some time last week), and yes, apple pay was disabled as well, a reboot to macos recovery and a change in security policy again fixed both things, while leaving my extensions disabled for that time, which eventually fixed it self when i again restored the Reduced Security setting. (until today {see above}, both time machine and apple pay were working fine in that mode on my mba m1 again)
- ***what I call pseudo extensions are those that are installed by say your dock, raid enclosure (both hw/sw ex. softraid by owc), or thunderbolt docks/hubs like those from CalDigit or virtual devices for specific video and audio software which do emulation or capturing, you can check them through system profiler when going to about this mac, then software > extensions. notice they are most likely not actually loaded by macos when you're logged in, but exist in a semi loaded state, and really only require to be installed for the software such as the Caldigit dock ejection utility or raid enclosures (like those from owc or others) to function.
- ****for example software from rogue amoeba installs the ACE component to hook into coreaudiod, which to macos acts like a kernel extension requiring the lower security setting, but isn't actually a typical kernel extension which loads when you login, the software of this company only requires it to be authenticated by the system and approved, they use the kernel extension method to accomplish this. which normally doesn't effect macos, unless there is a bug underlying in the security routine of macos which we now experience with monterey and on M-Series macs in particular.
Reading:
Extensions are moving away from the kernel
Management of kernel extensions has changed significantly in Big Sur and later. This overview for users contrasts kexts with user-level extensions which are replacing them.
"epic" (aka overlong and pointless) rant incoming:
I know software development is hugely complex. But Apple is perhaps the most profitable (or whatever, top 10) companies on the planet. The only reason the QC has dropped on its arse is because to actually dedicate the dev resources to get things working nicely again would cost more money.
I know I'm pointing out the obvious. But I've been in the Apple camp solidly since 2006 (always maintained some kind of Windows thing going on, hell I even had an iPAQ), and what upsets me - apart from the **** I have paid thousands of pounds for not working or having design flaws that aren't admitted to nor solutions offered for (I'm thinking of you, my darling AirPods Max, that I'm scared to even simply use now, even within the operating specs, because they keep trying to drown themselves. Did I listen to too much Radiohead and Nick Drake or something? Or was it the Jeff Buckley? (Respect to my fallen brothers, for real) Apple Support's response? Well, they were kind enough to link to their own support article on how to clean them, so basically "Gofe Yourself Sir") ahem what upsets me the most is that this is a clear, inexorable race to the bottom, and we're locked in for the sink - I know I am, based on the sheer amount of money I've thrown into this ecosystem that is more or less poisoning its inhabitants, especially anyone not near the top of every bell curve Tim rims year in year out. Not to mention the huge technical task it would take to migrate to a less geek-hostile platform, and the fact my octogenarian mum is also happily (very happily, thankfully) an inhabitant of my iCloud. I'm simply not well enough (can you tell?) to even begin to consider another platform at this point. Being an orchard dweller used to put a spring in my step. But watching this short-sighted money-chasing decay was a big part of why I quit being a """""""genius""""""" in 2013. Rather than a spring in my step, Apple is a weight on my shoulders.
How long until this rot spreads to the hardware division? Oh right. My AirPods Max. This is bad. Apple is on its way to validating every swivel-eyed criticism that the anti-Apple fanboys have been levelling at us for years: overpriced, superficially pretty, consumption-only, subscription based paperweights for fools.
Sorry everyone. I came here because my Monterey MBP won't let me "Browse Other Backup Disks" on a Catalina backup from my previous MBP, last updated earlier this year. I realise my rant helps nobody, least of all myself, and while you may think this could have been its own thread, I disagree. I just wanted to vent somewhere where I know people will at least know what I'm talking about.
I know I'm pointing out the obvious. But I've been in the Apple camp solidly since 2006 (always maintained some kind of Windows thing going on, hell I even had an iPAQ), and what upsets me - apart from the **** I have paid thousands of pounds for not working or having design flaws that aren't admitted to nor solutions offered for (I'm thinking of you, my darling AirPods Max, that I'm scared to even simply use now, even within the operating specs, because they keep trying to drown themselves. Did I listen to too much Radiohead and Nick Drake or something? Or was it the Jeff Buckley? (Respect to my fallen brothers, for real) Apple Support's response? Well, they were kind enough to link to their own support article on how to clean them, so basically "Gofe Yourself Sir") ahem what upsets me the most is that this is a clear, inexorable race to the bottom, and we're locked in for the sink - I know I am, based on the sheer amount of money I've thrown into this ecosystem that is more or less poisoning its inhabitants, especially anyone not near the top of every bell curve Tim rims year in year out. Not to mention the huge technical task it would take to migrate to a less geek-hostile platform, and the fact my octogenarian mum is also happily (very happily, thankfully) an inhabitant of my iCloud. I'm simply not well enough (can you tell?) to even begin to consider another platform at this point. Being an orchard dweller used to put a spring in my step. But watching this short-sighted money-chasing decay was a big part of why I quit being a """""""genius""""""" in 2013. Rather than a spring in my step, Apple is a weight on my shoulders.
How long until this rot spreads to the hardware division? Oh right. My AirPods Max. This is bad. Apple is on its way to validating every swivel-eyed criticism that the anti-Apple fanboys have been levelling at us for years: overpriced, superficially pretty, consumption-only, subscription based paperweights for fools.
Sorry everyone. I came here because my Monterey MBP won't let me "Browse Other Backup Disks" on a Catalina backup from my previous MBP, last updated earlier this year. I realise my rant helps nobody, least of all myself, and while you may think this could have been its own thread, I disagree. I just wanted to vent somewhere where I know people will at least know what I'm talking about.
I have quite a few years on you. I've used Apple Products since the beginning (1980's) In school, and then owned my own computers since the 90's. So I share your disappointment in where Apple has gone considering that I've seen where they were .
You have my admiration and sympathy. And that's what hurts the most: this company DID "ignite the personal computer revolution" as their corporate copy goes. And they certainly "put a ding in the Universe", as His Holiness put it. It's a bit like being a drug addict: the lows feel especially low by virtue of just how high you've flown. Not that I'd know, haha! (That was a lie). Would I feel more optimistic if the CEO seemed to have a passion for literally anything, besides possibly arranging the objects on his desk? I don't know. They're so much bigger now than when Steve finished up his time. Still, I feel he took personally the quality level of Apple's products and services. Tim and the board take shareholder returns personally. And that's jolly well it.
Apple For me has ALWAYS been about Steve Jobs, he made apple what it is. So when I got excited about the events and so on, it was because I was looking forward to seeing HIM, and what he came up with. Now, I still genuinely like and use Apple products, but without Steve, Apple is just another company. At least to me, and probably many others who would be considered Apple Vets.
I like Craig, I just don't know a lot about him. Every time I see him though, he seems like a very personable person.
Yes, he knows how to connect with his audience which is something Cook lacks I feel to some degree.
This gives a great insight into him, its a 50 minute talk he gave at the Banatao Auditorium at UC Berkeley" in 2019: "Questionable Advice from One Very Lucky Berkeley Engineer."
Thanks for the link. I've actually watched that video a while back. Maybe it's time to watch it again for a refresher
yes yes yes! this is also how i feel about it! and according to various sources, steve jobs intended to go that way too, after cook, though some other sources claim, if that spat at the top didn't happen those few years ago, it would've or could've maybe even should've been scott forestall, the 1 to 1 protégé of steve in many respects, but we all know what happened to him.
The Apple senior tech called me back yesterday and says there is no fix and they are working on one for the next Monterey update, but they are well aware of the issue at this point.
2 things come to mind.
1) I had wondered if this was a kernal issue because I had to lower my security in Recovery in order to run pro Audio recording equipment Universal Audio. I had thoughts that might have something to do with it, but I don't have the time or energy to set the security to full security and then hope Time Machine runs properly. That being said, before today, nobody had mentioned lowering the security protocols and so I don't think that's the only/root cause of the issue.
2) I'm well aware that beta testers knew there was an issue with TM and monterey in June (based on reddit/forum posts) and somehow believed they had solved it, but clearly not. Kind of frustrating that they pushed this release out with - what I believe - to be a pretty bad bug. Apple relies constantly on customers backing up via time machine to properly provide technical service. They can no longer do that until this is fixed, which should cause them a backlog of computer technical problems they would be hesitant to fix for customers.
So, this issue was indeed prevalent for the beta testers and yet I can't seem to pin point when they think it got resolved except for the fact that some of them posted in forums back in June saying "not an issue with new beta release", but provided no additional details. So, Apple got the message they had fixed this when they were never even close to having fixed it. No clue how that happened.
Most importantly, when does apple start paying their fan boys, who are the ones left to spend all their time on investigating their mistakes?
2 things come to mind.
1) I had wondered if this was a kernal issue because I had to lower my security in Recovery in order to run pro Audio recording equipment Universal Audio. I had thoughts that might have something to do with it, but I don't have the time or energy to set the security to full security and then hope Time Machine runs properly. That being said, before today, nobody had mentioned lowering the security protocols and so I don't think that's the only/root cause of the issue.
2) I'm well aware that beta testers knew there was an issue with TM and monterey in June (based on reddit/forum posts) and somehow believed they had solved it, but clearly not. Kind of frustrating that they pushed this release out with - what I believe - to be a pretty bad bug. Apple relies constantly on customers backing up via time machine to properly provide technical service. They can no longer do that until this is fixed, which should cause them a backlog of computer technical problems they would be hesitant to fix for customers.
So, this issue was indeed prevalent for the beta testers and yet I can't seem to pin point when they think it got resolved except for the fact that some of them posted in forums back in June saying "not an issue with new beta release", but provided no additional details. So, Apple got the message they had fixed this when they were never even close to having fixed it. No clue how that happened.
Most importantly, when does apple start paying their fan boys, who are the ones left to spend all their time on investigating their mistakes?