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.
New MBP 2016 Crashing During Time Machine Backup
- Thread starter TreadEverSoLightly
- Start date
- Sort by reaction score
Without reading through full thread, can someone confirm if the crash happens with several USB-C drives, or only LaCie Porsche drive (which I am using as well and I am unable to backup via Time Machine without it crashing).
My Apple support rep was asking me if I thought it was a LaCie support issue but I tend to think not.
My Apple support rep was asking me if I thought it was a LaCie support issue but I tend to think not.
I'm having similar issues with my 2016 MBP. In backing up about 750 GB, Time Machine seems to work fine connected via USB + USB>TB3 adapter as well as connected via Firewire 800 + FW>Minidisplay port + TB2>TB3 adapters.
However when I connect using the same Firewire configuration and use SuperDuper to back up I have a shut down at roughly the same location about half way through the backup process. Very repeatable.
Anyone determined whether the type of connection or the adapters used to get to the TB3 ports make a difference?
However when I connect using the same Firewire configuration and use SuperDuper to back up I have a shut down at roughly the same location about half way through the backup process. Very repeatable.
Anyone determined whether the type of connection or the adapters used to get to the TB3 ports make a difference?
I am having the exact same problem. I thought it was my drive. I went into the Apple Store and bought a new LaCie (USB-C) drive to use for time machine....same thing freezes while going through the backup.
I am encrypting my backup disk....you all doing that as well?
I can't seem to find one but is there a thread for this on the Apple support forums?
I am encrypting my backup disk....you all doing that as well?
I can't seem to find one but is there a thread for this on the Apple support forums?
I am encrypting my MacBook Pro 2016 HD using filevault as well as encrypting the Time Machine target drive. I also have one of the new LaCie Porsche design USB-C drives. And I am also experiencing the crash doing the time machine backup.
Once the crash occurs, just attaching the drive to the MacBook Pro will cause it to freeze in about 30 seconds. The cursor locks and the trackpad goes dead.
I can return the MacBook Pro through the weekend and I am wondering whether I should do so. Any thoughts on that?
Last edited:
My problem is identical to what you described. I contacted support and they were rather useless. I am waiting for 10.12.2 to release next week and crossing my fingers it's fixed.
I'm having exactly the same problems others have described here where the system crashes with CATERR errors when copying to any external drives - using Finder, Carbon Copy Cloner or Time Machine.
I've created a support case with Apple but have yet to hear back from them regarding a fix. Some people here seem to be reporting success with the new beta, however my concern is whether it's a known issue which is specifically fixed in the new OS update, or whether it might have been unintentionally fixed in the new update but not known about specifically which might mean it could come back again! Assuming it has actually been fixed at all, or is even fixable and is not a low level hardware controller or firmware issue
I've created a support case with Apple but have yet to hear back from them regarding a fix. Some people here seem to be reporting success with the new beta, however my concern is whether it's a known issue which is specifically fixed in the new OS update, or whether it might have been unintentionally fixed in the new update but not known about specifically which might mean it could come back again! Assuming it has actually been fixed at all, or is even fixable and is not a low level hardware controller or firmware issue
Last edited:
They know about it, they're just not admitting it. How could they possibly miss such a huge problem. First time shipping this interface, the only I/O on the model and somehow it didn't get tested.
I am calling BS with Apple, they just didn't want to miss the Christmas season.
Rumor has it 10.12.2 is the cure.
Last edited:
Updating to 10.12.2 beta5 solved the issue for me.
What I found VERY curious is that after installing beta5 on a separate volume, my main macOS installation (regular 10.12.1 that had previously been definitely afflicted with the issue mentioned here) also became stable. Since experimenting with beta5, I cannot invoke a crash during a copy operation. And believe me – I've tried!
As a hindsight, I started wondering if this is possible that during 10.12.2 beta5 installation any kind of EFI/SMC upgrade had been carried out. In these new Touch Bar-equipped Macs one can't really say when they're being rebooted etc.
Now (after 10.12.2 beta5 experiment, when even the regular OS install does not exhibit problematic behavior any longer) Boot ROM Version and SMC version reported by System Information (Apple menu > About This Mac > System Report...) are MBP132.0226.B08 and 2.37f19 respectively). It's for MLH12ZE (i.e. base 13-inch with Touch Bar). Can anyone check theirs SMC/Boot ROM version?
mess
I am on a MacBook Pro 2016 15" Model running Mac OS 10.12.1 and my details are:
Boot ROM Version: MBP133.0226.B00
SMC Version (system): 2.38f5
I have not booted to a volume with the 10.12.2 beta yet.
I am on a MacBook Pro 2016 15" Model running Mac OS 10.12.1 and my details are:
Boot ROM Version: MBP133.0226.B00
SMC Version (system): 2.38f5
I have not booted to a volume with the 10.12.2 beta yet.
Just got an email reply from Craig Federighi confirming it has indeed been fixed in the new beta! Phew...
'Hi David,
Sorry for the inconvenience!
We we have indeed fixed this issue in the latest Sierra public beta (10.12.2, available at beta.apple.com).
Thanks,
- craig'
'Hi David,
Sorry for the inconvenience!
We we have indeed fixed this issue in the latest Sierra public beta (10.12.2, available at beta.apple.com).
Thanks,
- craig'
Attachments
I'm not having crash issues, but the date of the latest backup when I click on the time machine icon in the toolbar is incorrect. Shows the day I originally set up the new MBP from my old MBP backup. When I go into the external hard drive and look at the latest folders it shows that it was clearly updated today (or whenever I back it up). Anyone else seen this problem or know how to fix?
I also just updated and can confirm a few things:
1) The CR2 file that caused a system crash 100% of the time now doesn't cause it. I've tried to recreate the failure and can't.
2) The Boot ROM & SMC have both been updated (2016 15" 2.9/460)
Boot ROM MBP133.0226.B08 SMC Version: 2.38f6
3) Time remaining for battery life has been removed however I *think that it's consuming or reporting less consumption anyway.
4) Still seeing artifacts under Spotlight Search bars although not 100%...about the same rate as before.
5) I'm still seeing black lines vertical & horizontal (as if trying to outline windows perhaps?) around the open windows in Time Machine.
6) I haven't been able to reproduce the green & red lines on the screen in a while even before the update but I will certainly report back if it reappears.
1) The CR2 file that caused a system crash 100% of the time now doesn't cause it. I've tried to recreate the failure and can't.
2) The Boot ROM & SMC have both been updated (2016 15" 2.9/460)
Boot ROM MBP133.0226.B08 SMC Version: 2.38f6
3) Time remaining for battery life has been removed however I *think that it's consuming or reporting less consumption anyway.
4) Still seeing artifacts under Spotlight Search bars although not 100%...about the same rate as before.
5) I'm still seeing black lines vertical & horizontal (as if trying to outline windows perhaps?) around the open windows in Time Machine.
6) I haven't been able to reproduce the green & red lines on the screen in a while even before the update but I will certainly report back if it reappears.
Last edited:
I can confirm the issue has been fixed for me on the 10.12.2 Beta! Just completed my first successful backup on the new machine whereas previously it would fail every time.
The crashes are less frequent, but I came home last night to a frozen system. Looking at Time Machine, it had finished backing up just a few minutes before, so I'm thinking there's a possibility that the system was still running, but not responsive.
This morning the system was fine after 8+ hours of inactivity.
Still not right, but better with the 10.2.2 Beta.
This morning the system was fine after 8+ hours of inactivity.
Still not right, but better with the 10.2.2 Beta.
Beta 10.12.2 solved the TM crash issue for me as well. Had a strange semi-lock up later in the day where the mouse would move and menus would work, but the windows were sluggish. A quick restart fixed it. Never saw that with 10.12.1. Could have been a fluke.
Thank you for sharing this SMC/Boot ROM-related information!
I have the same versions running. Those were probably the versions with which the machine has been launched.
I will more or less patiently wait for the update and keep my fingers crossed.
But one question regarding Time Machine, since my successful backup, the hourly backups have been going on. One or two times I had to reset the machine, because the system had hung.
I am now wandering if I should start with a new backup after 10.12.2 comes out, since the transmission has proved to be unreliable? I mean maybe some bad data transfer could still have taken place or would Time Machine let me know if something were not as it should be?