Sidebar Sidebar
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

Clean install on a new partition did not help.
I am not doing a backup though, but copying a large 2,5 TB FCPX library from one external disk to another.
Nailed it down to one .mov file which caused the crash, on Finder Copy or Carbon Copy Cloner.
Reported everything to Apple.
Backups are running fine. No issues.
 
I'm seeing the same issue. I have a macbook pro 13" late 2016 with a 5TB external USB drive connected via a USB-C hub (Cable Matters). I selected that external drive with Time Machine and when the backup starts and freezes and than crashes and reboots the machine. This needs to be fixed ASAP

btw..it seems to be related to just Time Machine as I can copy large files across several external drives and my machbook pro..that seems to work
 
Last edited:
I'm having the same issue while using Carbon Copy Cloner (CCC) to create a full clone.

MacBook Pro 15" late 2016 w/touchbar. 2TB SSD. I am attempting to back up to a 3TB LaCie using apple's USB-C to USB3 adapter.

Everything seems like it is going fine, until the system freezes up. CCC shows a message that the destination volume dissapeared. The OS displays a message that the disk was not ejected properly. CPUs are pinned. Then the machine restarts.
 
  • Like
Reactions: AlanDD
asah said:
I'm having the same issue while using Carbon Copy Cloner (CCC) to create a full clone.

MacBook Pro 15" late 2016 w/touchbar. 2TB SSD. I am attempting to back up to a 3TB LaCie using apple's USB-C to USB3 adapter.

Everything seems like it is going fine, until the system freezes up. CCC shows a message that the destination volume dissapeared. The OS displays a message that the disk was not ejected properly. CPUs are pinned. Then the machine restarts.
Click to expand...

Please, everybody, call Apple support! They need more input in order to fix it.
[doublepost=1480275139][/doublepost]By the way I did a 900 Gb backup with CCC. No issues.
 
Just had an apple support chat on this and predictably the support gentleman went down the path of trying to solve my specific issue (implying an issue with my installed 3rd party software) without any acknowledgement that this may be a widespread issue that needs to be dealt with by Apple corp.

I tried to point him to this thread which led to this humorous exchange:

Me: If you read that thread [Meaning this macrumors thread] you will see people have the same issue with these computers regardless of whether they ran migration assistant or not

Jon@Apple Support: Lot’s of people say Santa Clause exists. The point being on that, most of those people have posted without contact us to truly determine the cause and solution for it.

I think we need to keep hammering on this because as far as I can tell right now, this does not seem to be escalating at Apple.
 
I've notified Apple support of the following:


  • *Any* hard drive, of any kind, on *any* of the four USB-C ports, connected on *any* cable type (USB-C 3.1 Gen 2 on both ends, USB C 3.1 Gen 2 to USB 3 1.0 adapter, connecting hard-drive mfg-provided USB cable), all Apple cables plugged into the machine (no third party cables in the physical USB-C ports of the MBP itself), hard crashes machine during encrypted TimeMachine backup (with a freshly formatted drive)

    High bandwidth (the new 2TB SSD drives, like Samsung T-3) drives crash faster.


  • I sent the link to this thread so they have it. https://forums.macrumors.com/threads/new-mbp-2016-crashing-during-time-machine-backup.2017003/

    I noted for them my own experience that the current beta of OS X 10.12.2 (release 3) does not fix the problem.

    Confirmed on TWO separate, IDENTICAL, brand new, MacBook Pro 15", touchbar, 16GB memory, 2TB SSD, quad core CPU machines, each running in safe mode.

    Tested on ALL ports. On ALL cable combinations. On 10.12.1 and 10.12.2

    CLEAN install, no other software running (for 10.12.2 beta)

    In ALL cases, an attempt to perform an encrypted TimeMachine backup to a FRESH formatted drive of ANY manufacturer produces a CATERR hard crash.

    Being unable to back up makes the hardware unusable.

In general, these machines, along with weird external monitor artefacts (odd blanking, flickering) through the Apple-required usb-c digital-av-multiport adapter (http://www.apple.com/shop/product/MJ1K2AM/A/usb-c-digital-av-multiport-adapter) to 4K displays, are feeling like pieces of ****.

It's beyond abusive for Apple to have tested $5k hardware so little as to miss these basic issues.

 
Jason Bourne said:
Just had an apple support chat on this and predictably the support gentleman went down the path of trying to solve my specific issue (implying an issue with my installed 3rd party software) without any acknowledgement that this may be a widespread issue that needs to be dealt with by Apple corp.

I tried to point him to this thread which led to this humorous exchange:

Me: If you read that thread [Meaning this macrumors thread] you will see people have the same issue with these computers regardless of whether they ran migration assistant or not

Jon@Apple Support: Lot’s of people say Santa Clause exists. The point being on that, most of those people have posted without contact us to truly determine the cause and solution for it.

I think we need to keep hammering on this because as far as I can tell right now, this does not seem to be escalating at Apple.
Click to expand...
unbelievable. They just need one of their expensive new MacBooks and put ANY usb drive in, wait for some minutes - it crashes. Maybe it is time to look ahead and say goodbye to Apple arrogance...
[doublepost=1480347375][/doublepost]We should try to contact blogs and news sites about this. I already contacted germanys most read computer news site heise.de about this. Hope they will care about this.
 
I have done several new TM backups as a test, and I haven't had any more problems, since that first time with the factory install of OS, when TM hung up and I had reboot and start again. CCC is working as it should as well.
 
I am also experiencing this issue. I have an 2x8TB RAID1 enclosure connected by USB-C (via a USB hub). Time machine has failed twice now. I contacted Apple Care online and one of the steps he suggested was resetting NVRAM and SMC. I am reluctant to do that because I think it has nothing to do with the issue? Has anyone tried those steps? I see one or two people claim a fresh install has worked for them -- should I try that? I'd really like to start backing up my stuff.

Also, are you people all having trouble with encrypted or non-encrypted backups? For me, I've been doing encrypted backups.

My machine will crash, and then if I enter the time machine password, it will crash again. I cannot enter my time machine password without my macbook immediately crashing.
 
Great job Apple has done with this machine... I'm tempted to go back to my 2014 MBP that is a bit slower but at least works fine...
 
dlynch158 said:
I am also experiencing this issue. I have an 2x8TB RAID1 enclosure connected by USB-C (via a USB hub). Time machine has failed twice now. I contacted Apple Care online and one of the steps he suggested was resetting NVRAM and SMC. I am reluctant to do that because I think it has nothing to do with the issue? Has anyone tried those steps? I see one or two people claim a fresh install has worked for them -- should I try that? I'd really like to start backing up my stuff.

Also, are you people all having trouble with encrypted or non-encrypted backups? For me, I've been doing encrypted backups.

My machine will crash, and then if I enter the time machine password, it will crash again. I cannot enter my time machine password without my macbook immediately crashing.
Click to expand...
Setting up a clean install does not change anything for me. NVRAM and SMC advice ist like "I have no further idea...", so some people tried without success. My Time Machine backup was not encrypted btw.
 
dlynch158 said:
I am also experiencing this issue. I have an 2x8TB RAID1 enclosure connected by USB-C (via a USB hub). Time machine has failed twice now. I contacted Apple Care online and one of the steps he suggested was resetting NVRAM and SMC. I am reluctant to do that because I think it has nothing to do with the issue? Has anyone tried those steps? I see one or two people claim a fresh install has worked for them -- should I try that? I'd really like to start backing up my stuff.

Also, are you people all having trouble with encrypted or non-encrypted backups? For me, I've been doing encrypted backups.

My machine will crash, and then if I enter the time machine password, it will crash again. I cannot enter my time machine password without my macbook immediately crashing.
Click to expand...
No TM encryption here. I think you will be better served trying a clean install, versus what the tech suggested. This is a software issue. Restting SMC and NVRAM is a waste of time.
 
My setup is encrypted TM backup over Belkin ethernet dongle to Synology NAS. Perhaps the problem is the encryption software/hardware.

EDIT: I see other people are not using encryption. So it's probably not the encryption module.
 
Last edited:
I'm not using encryption for the backups and they are crashing out for me on two different USB-C backup drives. Cant really tell if they are crashing at the same spot or not.
 
Tldr: I confirm what "lietsche" already said that the crash occurs upon a transfer of a single "corrupt" file. In my case only one .jpg file inside my iPhotos library. (there might be more corrupt files, but this is the first one that I have encountered)

longer: I have the new BMP 13" with touch-bar 2.9MHz intel5 with 8Gb memory. It crashed on Friday for the first time while transferring my iTunes, Documents and iPhoto files/libraries from my time machine HD to a brand new exFAT formatted HD (using Apple USB-C to USB adapter and the HD's own micro USB-B to USB cable). After the crash, the external HD could not be mounted, and disk utility was not able to see it. In terminal, I used "diskutil -list" to observe it. Then I unmounted and mounted it back. This solved the disk problem. I checked (first aid in disk utility under recovery mode of the MBP) all my drives (internal, time machine HD and the external HD), showing no error.

Then I transferred my Documents without a problem. Then my iTunes library without a problem. Then the iPhoto library transfer reproduced the crash. At this point, I also bought a direct USB-C to micro USB-B cable for the external HD, in order to eliminate any connection mismatch. No avail, MBP crash is persistent.

I contacted the Apple support and had a long telephone call that at the end suggested directory by directory and file by file transfer in order to find the culprit. Now I have the file that causes the problem and will send it to apple.

However, this seems to be an OS problem as no transfer should trigger a computer crash. A transfer fault should trigger an error message only.

Can you try if the attached file also cause a crash in your MBP's? I do not detect a virus in the file. Please, can someone check this as well? (Well the file is too large (4.1Mb) for the macrumors server, so ask me personally and I will send it to you by e-mail)

with kind regards,
riza
 
Can you upload the file to dropbox or similar and link it? That's probably easier. I'll be glad to try, as my MBP15 has been rock stable so far.
 
ManuCH said:
Can you upload the file to dropbox or similar and link it? That's probably easier. I'll be glad to try, as my MBP15 has been rock stable so far.
Click to expand...

https://dl.dropboxusercontent.com/u/30972446/DSC_0581.JPG

I will keep the link only for few days. Please also keep in mind that the people in the photo are real and do not use it for no other purpose but to test the current MBP crashing issue. I can open the file in preview without no problem. So I actually do not understand what makes the MBP crash!? I will be very happy if someone can reproduce the crash.

Regards,
Riza
 
So what do I need to do? Just download the file and try to copy it via USB-C to an external disk? Or does it need to be a larger transfer to reproduce it?

It will be 24 hours until I can try as I'm not with my MBP at the moment.
 
ManuCH said:
So what do I need to do? Just download the file and try to copy it via USB-C to an external disk? Or does it need to be a larger transfer to reproduce it?

It will be 24 hours until I can try as I'm not with my MBP at the moment.
Click to expand...

I transferred the file from my desktop to the "external HD/iphotoslibrary/Masters/2016/05/.../.../" Where the iphotos library contained the leftover from my previous full transfer attempt. This triggered the crash after I confirm the replacement of the same file on the external HD.

edit: Apparently it was another file that caused it or maybe in combination with the first one that I have posted. Here is the link to the second file.

https://dl.dropboxusercontent.com/u/30972446/DSC_0582.JPG

and here is the proof

https://dl.dropboxusercontent.com/u/30972446/DC9274DD-1292-4830-85A8-A7B3F58FBE48.JPG

regards,
Riza
 
Last edited:
The public beta has also been released, for anyone who wants to test against this problem. I think the problem is too new for Apple to have specifically addressed it with this beta. However, fixing one bug could have fixed other related ones.
 
Riza this is great!! I can confirm this second image (DSC_0582.JPG) crashes my machine with the same symptoms as my own issue transferring a large DMG file. The crash from attempting to copy your JPG file results in a Kernel Panic with the same type of output as my issue.

Copying the file internally to another partition, and wirelessly to another mac, works fine. Also, downloading that file on my older macmini running 10.9.5 and copying to an external drive works fine. Finally, and this is important, once the file is on the external drive I CAN copy it back to the mac, but then trying to copy it back to the external drive results in a crash.

This to me is almost perfect proof that this is an issue related to outgoing USB-C transfers on the 2016 macbook pros.
 
  • Like
Reactions: Poofy1971
deutsched said:
Riza this is great!! I can confirm this second image (DSC_0582.JPG) crashes my machine with the same symptoms as my own issue transferring a large DMG file. The crash from attempting to copy your JPG file results in a Kernel Panic with the same type of output as my issue.

Copying the file internally to another partition, and wirelessly to another mac, works fine. Also, downloading that file on my older macmini running 10.9.5 and copying to an external drive works fine. Finally, and this is important, once the file is on the external drive I CAN copy it back to the mac, but then trying to copy it back to the external drive results in a crash.

This to me is almost perfect proof that this is an issue related to outgoing USB-C transfers on the 2016 macbook pros.
Click to expand...

Hahaha! :) we nailed it! Thanks for the confirmation. I tried to send the file to Apple but they do not accept any files by e-mail and there is no web site that I can drop it. I arranged another phone call for wednesday. I will ask for the method of file transfer then.

Cheers,
Riza
 
riza.dervisoglu said:
Hahaha! :) we nailed it! Thanks for the confirmation. I tried to send the file to Apple but they do not accept any files by e-mail and there is no web site that I can drop it. I arranged another phone call for wednesday. I will ask for the method of file transfer then.

Cheers,
Riza
Click to expand...

When you talk to them, tell them you'd like to escalate the case to engineering, and request that they set you up with their "gigafiles" system so you can send them the file. This should be an open and shut case at this point. 1) Download file onto 2016 MacBook Pro. 2) Try to transfer file via USB to external harddrive/flashdrive. 3) Watch computer freeze and reboot. 4) Fix it already, Apple.
 
  • Like
Reactions: Poofy1971
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back