Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Initial time machine backup crashes Yosemite 10.10.3

I have a 15" Macbook Pro 2.3 GHz Intel Core i7 running Yosemite 10.10.3 (14D136). I previously had a 1TB Time Capsule that ran pretty much without a problem. I recently upgraded to a new 3TB time capsule (http://store.apple.com/us/product/ME182LL/A/airport-time-capsule-3tb).


I have attempted numerous times to complete the initial backup both via wifi and hardwired into the thunderbolt port. It will run for an hour or so then just says (stopping). After that the computer gives me the pinwheel of death. After a restart everything runs fine and can restart process but same things happens. I have about 720GB to transfer so it takes a while (10 hrs or so). Every time I return it has stopped. I have erased and reinitialized the time capsule disk several times.

MacBook Pro (Retina, 15-inch, Late 2013), OS X Yosemite (10.10.3)

Posted on Apr 18, 2015 5:00 AM

Reply
3 replies

Apr 18, 2015 8:40 AM in response to CMactrouble

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

Step 1

For this step, the title of the Console window should be All Messages. If it isn't, select

SYSTEM LOG QUERIES All Messages

from the log list on the left. If you don't see that list, select

View Show Log List

from the menu bar at the top of the screen.

In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter "BOOT_TIME" (without the quotes.)

Each message in the log begins with the date and time when it was entered. Select the BOOT_TIME log message that corresponds to the last boot time when you had the problem. Now clear the search box to reveal all messages. Select the ones logged before the boot, during the time something abnormal was happening. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

For example, if the system was unresponsive or was failing to shut down for three minutes before you forced a restart, post the messages timestamped within three minutes before the boot time, not after. Please include the BOOT_TIME message at the end of the log extract—not at the beginning.

If there are long runs of repeated messages, please post only one example of each. Don’t post many repetitions of the same message.

When posting a log extract, be selective. A few dozen lines are almost always more than enough.

Some private information, such as your name, may appear in the log. Anonymize before posting.

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

Step 2

In the Console window, select

DIAGNOSTIC AND USAGE INFORMATION System Diagnostic Reports

(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select

View Show Log List

from the menu bar.

There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A crash report has a name that begins with the name of the crashed process and ends in ".crash". A panic report has a name that begins with "Kernel" and ends in ".panic". A shutdown stall report has a name that ends in ".shutdownstall". Select the most recent of each, if any. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot. It's possible that none of these reports exists.

I know the report is long, maybe several hundred lines. Please post all of it anyway.

If you don't see any reports listed, but you know there was a crash or panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

When you post the log extract or the crash report, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

Apr 18, 2015 5:56 PM in response to CMactrouble

The same thing keeps happending. I erase and format the 3T time capsule. The back up will start and back up roughly 240 gigs (until the drive reads 2.76 T Avail). Then it crashes, seems to be the same place everytime. This was the crash report


Anonymous UUID:



Sat Apr 18 20:43:57 2015



*** Panic Report ***

panic(cpu 2 caller 0xffffff80133c1cde): "launchd died\nState at Last Exception:\n\n"@/SourceCache/xnu/xnu-2782.20.48/bsd/kern/kern_exit.c:363



Mac OS version: 14D136

Kernel version: Darwin Kernel Version 14.3.0: Mon Mar 23 11:59:05 PDT 2015; root:xnu-2782.20.48~5/RELEASE_X86_64

Kernel UUID: 4B3A11F4-77AA-3D27-A22D-81A1BC5B504D

System model name: MacBookPro11,3 (Mac-2BD1B31983FE1663)

Model: MacBookPro11,3, BootROM MBP112.0138.B14, 4 processors, Intel Core i7, 2.3 GHz, 16 GB, SMC 2.19f12

Graphics: Intel Iris Pro, Intel Iris Pro, Built-In

Graphics: NVIDIA GeForce GT 750M, NVIDIA GeForce GT 750M, PCIe, 2048 MB

Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020

Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x134), Broadcom BCM43xx 1.0 (7.15.166.24.3)

Bluetooth: Version 4.3.4f4 15601, 3 services, 18 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en0

Serial ATA Device: APPLE SSD SM1024F, 1 TB

USB Device: Internal Memory Card Reader

USB Device: BRCM20702 Hub

USB Device: Bluetooth USB Host Controller

USB Device: Apple Internal Keyboard / Trackpad

Thunderbolt Bus: MacBook Pro, Apple Inc., 17.1

Apr 18, 2015 6:12 PM in response to CMactrouble

Make a "Genius" appointment at an Apple Store, or go to another authorized service provider. You may have to leave the machine there for several days.

Back up all data on the internal drive(s) before you hand over your computer to anyone. There are ways to back up a computer that isn't fully functional—ask if you need guidance.

If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.

Keeping your confidential data secure during hardware repair

Apple also recommends that you deauthorize a device in the iTunes Store before having it serviced.

*An SSD doesn't need to be zeroed.

Initial time machine backup crashes Yosemite 10.10.3

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.