Time machine to SSD

Question

Time machine to SSD

Hey there,

I have a Mac Pro with two 1TB drives. One is my OS drive and the other is TM. I recently installed a 256 Gb SSD to migrate the OS over to but it wasn't working since TM can't restore to a drive smaller than it's origin drive apparently.

I surmised that since my "disk usage" is only about 115Gb that I could simply create a 210Gb (making sure to be more than my usage but less than my SSD space) partition on an external drive. From there I'd back up TM to the partition and when reinstalling mountain lion I could simply "restore from time machine backup" from the 210Gb partition to my 256Gb SSD.

Problem: I receive no error message but I've had the "Cleaning up" message for 12 hours on 3 different tries. Things I've tried:

- Made sure spotlight wasn't indexing the external

- reformatted the external so it only had one partition and rest was "free space".

- Taking out the old TM backup drive to prevent confusion

I'm at a loss and would appreciate any help.

Brian

Posted on Jul 26, 2013 6:09 AM

Reply

Answer 1

Linc Davis

Level 10

209,535 points

Jul 26, 2013 10:06 AM in response to briansterling

If you have more than one user account, these instructions must be carried out as an 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. Click Utilities, then Console in the icon grid.

Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select

View ▹ Show Log List

from the menu bar.

Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message that corresponds to a failed backup. Now

CLEAR THE WORD "Starting" FROM THE TEXT FIELD

so that all messages are showning, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them (command-C) to the Clipboard. Paste (command-V) into a reply to this message.

If all you see are messages that contain the word "Starting," you didn't clear the text field.

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

When posting a log extract, be selective. Don't post more than is requested.

Please do not indiscriminately dump thousands of lines from the log into this discussion.

Some personal information, such as the names of your files, may be included — anonymize before posting.

Reply

Answer 2

Jul 26, 2013 2:10 PM in response to Linc Davis

Thanks for the reply. I had 6 messages that popped up under "starting". First one was at 9:58AM so I posted the logs from a few minutes before and after that time because I'm not sure what I'm looking for. It came up as "LKDCHelper: Starting (uid=502)". It also occured three more times and the other two "starting" messages were from GoogleSoftwareUpdateDaemon. Thank you very much.

******************************

7/26/13 9:57:14.262 AM bootpd[110]: service time 0.000015 seconds

7/26/13 9:57:16.271 AM bootpd[110]: service time 0.000017 seconds

7/26/13 9:57:23.388 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon[25535]) Job failed to exec(3) for weird reason: 13

7/26/13 9:57:23.388 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds

7/26/13 9:57:33.391 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon[25537]) Job failed to exec(3) for weird reason: 13

7/26/13 9:57:33.391 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds

7/26/13 9:57:34.393 AM bootpd[110]: service time 0.000008 seconds

7/26/13 9:57:41.622 AM configd[56]: inet_set_autoaddr(en0, 1) failed, Resource busy (16)

7/26/13 9:57:43.395 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon[25538]) Job failed to exec(3) for weird reason: 13

7/26/13 9:57:43.395 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds

7/26/13 9:57:53.398 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon[25539]) Job failed to exec(3) for weird reason: 13

7/26/13 9:57:53.398 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds

7/26/13 9:57:54.561 AM bootpd[110]: service time 0.000015 seconds

7/26/13 9:57:55.017 AM bootpd[110]: service time 0.000006 seconds

7/26/13 9:58:03.402 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon[25541]) Job failed to exec(3) for weird reason: 13

7/26/13 9:58:03.402 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds

7/26/13 9:58:05.854 AM bootpd[110]: service time 0.000009 seconds

7/26/13 9:58:06.656 AM bootpd[110]: service time 0.000008 seconds

7/26/13 9:58:07.662 AM bootpd[110]: service time 0.000016 seconds

7/26/13 9:58:12.994 AM bootpd[110]: service time 0.000008 seconds

7/26/13 9:58:13.406 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon[25543]) Job failed to exec(3) for weird reason: 13

7/26/13 9:58:13.406 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds

7/26/13 9:58:23.410 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon[25544]) Job failed to exec(3) for weird reason: 13

7/26/13 9:58:23.410 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds

7/26/13 9:58:24.375 AM bootpd[110]: service time 0.000016 seconds

7/26/13 9:58:27.969 AM bootpd[110]: service time 0.000007 seconds

7/26/13 9:58:33.414 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon[25545]) Job failed to exec(3) for weird reason: 13

7/26/13 9:58:33.414 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds

7/26/13 9:58:37.736 AM bootpd[110]: service time 0.000008 seconds

7/26/13 9:58:42.589 AM bootpd[110]: service time 0.000015 seconds

7/26/13 9:58:43.418 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon[25546]) Job failed to exec(3) for weird reason: 13

7/26/13 9:58:43.418 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds

7/26/13 9:58:50.547 AM bootpd[110]: service time 0.000007 seconds

7/26/13 9:58:53.421 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon[25550]) Job failed to exec(3) for weird reason: 13

7/26/13 9:58:53.421 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds

7/26/13 9:58:58.859 AM LKDCHelper[25552]: Starting (uid=502)

7/26/13 9:58:59.401 AM AddressBookSourceSync[25549]: *** -[IADomainCache init]: IA domains cache couldn't be read.

7/26/13 9:59:00.721 AM bootpd[110]: service time 0.000007 seconds

7/26/13 9:59:03.425 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon[25555]) Job failed to exec(3) for weird reason: 13

7/26/13 9:59:03.425 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds

7/26/13 9:59:10.000 AM bootpd[110]: service time 0.000015 seconds

7/26/13 9:59:11.478 AM bootpd[110]: service time 0.000007 seconds

7/26/13 9:59:13.430 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon[25557]) Job failed to exec(3) for weird reason: 13

7/26/13 9:59:13.430 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds

7/26/13 9:59:21.961 AM bootpd[110]: service time 0.000008 seconds

7/26/13 9:59:23.435 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon[25558]) Job failed to exec(3) for weird reason: 13

7/26/13 9:59:23.435 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds

7/26/13 9:59:25.757 AM bootpd[110]: service time 0.000008 seconds

7/26/13 9:59:33.438 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon[25562]) Job failed to exec(3) for weird reason: 13

7/26/13 9:59:33.438 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds

7/26/13 9:59:35.265 AM bootpd[110]: service time 0.000008 seconds

7/26/13 9:59:37.415 AM bootpd[110]: service time 0.000008 seconds

7/26/13 9:59:42.283 AM bootpd[110]: service time 0.000008 seconds

7/26/13 9:59:43.443 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon[25563]) Job failed to exec(3) for weird reason: 13

7/26/13 9:59:43.443 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds

7/26/13 9:59:49.190 AM configd[56]: inet_set_autoaddr(en0, 1) failed, Resource busy (16)

7/26/13 9:59:51.588 AM bootpd[110]: service time 0.000008 seconds

7/26/13 9:59:51.711 AM bootpd[110]: service time 0.000005 seconds

7/26/13 9:59:53.448 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon[25564]) Job failed to exec(3) for weird reason: 13

7/26/13 9:59:53.448 AM com.apple.launchd.peruser.502[169]: (com.wondershare.mobilegodaemon) Throttling respawn: Will start in 10 seconds

7/26/13 9:59:54.519 AM bootpd[110]: service time 0.000008 seconds

7/26/13 9:59:54.668 AM bootpd[110]: service time 0.000005 seconds

*************************************

Reply

Answer 3

Linc Davis

Level 10

209,535 points

Jul 26, 2013 5:05 PM in response to briansterling

There's no indication of any Time Machine activity in that log extract.

Click the Clear Display icon in the toolbar of the Console window. Then select Back Up Now from the Time Machine menu. Post any messages that appear in the window.

Reply