Time machine stuck after "Ownership is disabled..."
Hi,
I have a problem with Time Machine + Time Capsule on my Mac Pro.
1 week ago all was working properly, but now I'm not able anymore the complete the initial backup.
Here is what I have in the log :
04/10/13 11:23:54,018 com.apple.backupd[1696]: Starting automatic backup
04/10/13 11:23:54,038 com.apple.backupd[1696]: Attempting to mount network destination URL: afp://jocelyn%20fournier;[email protected]/Time%20Capsule%20 Lia%20_%20Joce
04/10/13 11:23:54,486 com.apple.backupd[1696]: Mounted network destination at mount point: /Volumes/Time Capsule Lia _ Joce using URL: afp://jocelyn%20fournier;[email protected]/Time%20Capsule%20 Lia%20_%20Joce
04/10/13 11:23:58,111 com.apple.backupd[1696]: User continued after being warned of changed destination volume identity
04/10/13 11:23:58,128 com.apple.backupd[1696]: Creating disk image /Volumes/Time Capsule Lia _ Joce/Mac Pro de jocelyn fournier.sparsebundle
04/10/13 11:24:34,198 com.apple.backupd[1696]: Failed to hide extension on /Volumes/Time Capsule Lia _ Joce/Mac Pro de jocelyn fournier.sparsebundle, error: Error Domain=NSCocoaErrorDomain Code=4 "The file “Mac Pro de jocelyn fournier.sparsebundle” doesn’t exist." UserInfo=0x7fbb91c1a2f0 {NSURL=file://localhost/Volumes/Time%20Capsule%20Lia%20_%20Joce/Mac%20Pro%20de% 20jocelyn%20fournier.sparsebundle/, NSFilePath=/Volumes/Time Capsule Lia _ Joce/Mac Pro de jocelyn fournier.sparsebundle, NSUnderlyingError=0x7fbb91c19970 "The operation couldn’t be completed. No such file or directory"}.
04/10/13 11:24:40,606 com.apple.backupd[1696]: Disk image /Volumes/Time Capsule Lia _ Joce/Mac Pro de jocelyn fournier.sparsebundle mounted at: /Volumes/Copies de sauvegarde Time machine
04/10/13 11:24:40,611 com.apple.backupd[1696]: Backing up to: /Volumes/Copies de sauvegarde Time machine/Backups.backupdb
04/10/13 11:24:40,616 com.apple.backupd[1696]: Ownership is disabled on the backup destination volume. Enabling.
Nothing is happening after this point, and Time Machine is stuck in the state 'Preparing backup...'
The time capsule is connected directly through ethernet.
I've tried the same setup on an iMac, and all is working perfectly, so I assume there's somework wrong on the Mac Pro.
Here's what I have already tried :
- Reformat the time capsule
- Fix permission on the Mac Pro
- Start the mac pro in Safe mode
- Let the time capsule alone on the ethernet port (wifi is disabled)
- Changing the name of the time capsule partition
- Reselecting the time capsule through the 'choose disk' button
- Enabling / Disabling trim on my main SSD disk
Here is what I can see on the time capsule :
-rwxrwxrwx@ 1 root wheel 0 4 oct 10:26 .com.apple.timemachine.supported
drwxrwxrwx@ 1 root wheel 264 4 oct 11:44 Mac Pro de jocelyn fournier.sparsebundle
drwxrwxrwx@ 1 root wheel 264 4 oct 11:44 iMac de Jocelyn.sparsebundle
drwxrwxrwx@ 1 root wheel 264 4 oct 11:44 .
drwx------ 1 root wheel 264 4 oct 11:24 ..
-rwxrwxrwx 1 root wheel 500 4 oct 11:23 Info.bckup
-rwxrwxrwx 1 root wheel 500 4 oct 11:23 Info.plist
drwxrwxrwx 1 root wheel 3730 4 oct 11:43 bands
-rwxrwxrwx 1 root wheel 445 4 oct 11:24 com.apple.TimeMachine.MachineID.bckup
-rwxrwxrwx 1 root wheel 445 4 oct 11:24 com.apple.TimeMachine.MachineID.plist
-rwxrwxrwx 1 root wheel 0 4 oct 11:23 token
[root@Mac-Pro-de-jocelyn-fournier] /Volumes/Time Capsule Lia _ Joce/Mac Pro de jocelyn fournier.sparsebundle/bands> l
total 1705048
drwxrwxrwx 1 root wheel 3730 4 oct 11:43 .
drwxrwxrwx@ 1 root wheel 264 4 oct 11:44 ..
-rwxrwxrwx 1 root wheel 3264512 4 oct 11:23 0
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 19
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1a
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1b
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1c
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1c9
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1ca
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1cb
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1cc
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1cd
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1ce
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1cf
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1d
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1d0
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1d1
-rwxrwxrwx 1 root wheel 4775936 4 oct 11:23 1d145
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1d2
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1d3
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1d4
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1d5
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1d6
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1d7
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1d8
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1d9
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1da
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1db
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1dc
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1dd
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1de
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1df
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1e
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1e0
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1e1
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1e2
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1e3
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1e4
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1e5
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1e6
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1e7
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1e8
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1e9
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1ea
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1eb
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1ec
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1ed
-rwxrwxrwx 1 root wheel 184320 4 oct 11:24 1ee
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 1f
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 20
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 21
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 22
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 23
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 24
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 25
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 26
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 27
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 28
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 29
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 2a
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 2b
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 2c
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 2d
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 2e
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 2f
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 30
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 31
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 32
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 33
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 34
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 35
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 36
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 37
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 38
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 39
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 3a
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:23 3a271
-rwxrwxrwx 1 root wheel 1077248 4 oct 11:24 3a272
-rwxrwxrwx 1 root wheel 1097728 4 oct 11:23 3a282
-rwxrwxrwx 1 root wheel 24576 4 oct 11:24 3a9
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 3b
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 3c
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 3d
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 3e
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 3f
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 40
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 41
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 42
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 43
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 44
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 45
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 46
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 47
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 48
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 49
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 4a
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 4b
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 4c
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 4d
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 4e
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 4f
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 50
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 51
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 52
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 53
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 54
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 55
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 56
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 57
-rwxrwxrwx 1 root wheel 8388608 4 oct 11:24 58
-rwxrwxrwx 1 root wheel 6475776 4 oct 11:24 59
And the mounted backup :
[root@Mac-Pro-de-jocelyn-fournier] /Volumes/Copies de sauvegarde Time machine> l <11:48:15
total 0
drwxr-xr-x 4 root wheel 272 4 oct 11:24 .
drwxrwxrwt@ 10 root admin 340 4 oct 11:39 ..
d-wx-wx-wt@ 2 _unknown _unknown 68 4 oct 11:24 .Trashes
drwx------ 2 _unknown _unknown 102 4 oct 11:24 .fseventsd
Any clues of what could be wrong here ?
(the mounting seems really strange to me, especially the ownership)
Thanks,
Jocelyn
Well, 2h after trying to launch the backup, mds finally crashed, and it seems this unlocked the backup :
04/10/13 17:02:41,785 ReportCrash[3841]: DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.
04/10/13 17:02:42,849 ReportCrash[3841]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
04/10/13 17:02:42,849 ReportCrash[3841]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
04/10/13 17:02:42,849 ReportCrash[3841]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
04/10/13 17:02:42,849 ReportCrash[3841]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
04/10/13 17:02:42,849 ReportCrash[3841]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
04/10/13 17:02:42,849 ReportCrash[3841]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
04/10/13 17:02:42,849 ReportCrash[3841]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
04/10/13 17:02:42,849 ReportCrash[3841]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
04/10/13 17:02:42,850 ReportCrash[3841]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
04/10/13 17:02:42,850 ReportCrash[3841]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
04/10/13 17:02:42,967 com.apple.launchd[1]: (com.apple.metadata.mds[77]) Job appears to have crashed: Segmentation fault: 11
04/10/13 17:02:43,008 mds[3842]: (Normal) FMW: FMW 0 0
04/10/13 17:02:43,213 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,214 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,214 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,214 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,215 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,215 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,215 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,216 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,216 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,216 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,216 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,217 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,217 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,217 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,217 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,218 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,218 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,218 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,218 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,219 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,219 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,219 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,219 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,219 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,220 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,220 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,220 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,220 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,221 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,221 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,221 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,221 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,222 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,222 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,222 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,222 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,223 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,223 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,223 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,224 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,224 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,224 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,224 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,225 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,225 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,225 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,225 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,226 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,226 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,226 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,226 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,227 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,227 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,227 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,227 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,228 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,228 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,228 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,228 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,228 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,229 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,229 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,229 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,229 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,230 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,230 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,230 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,230 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,231 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,231 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,231 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,231 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,231 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,232 mds[3842]: (Error) Task: Invalid storeTokenID (6b000010) in MDSFetchTask
04/10/13 17:02:43,232 mds[3842]: (Error) Task: Invalid storeTokenID (6b000000) in MDSFetchTask
04/10/13 17:02:43,232 mds[3842]: (Error) Task: Invalid storeTokenID (6b000000) in MDSFetchTask
04/10/13 17:02:43,316 com.apple.backupd[2263]: Forcing deep traversal on source: "SSD" (mount: '/' fsUUID: 1ECDA662-9676-3D18-9939-C8D073A15B37 eventDBUUID: 14D09399-8E05-4F8C-993F-2707EF8DEE2D)
04/10/13 17:02:43,316 com.apple.backupd[2263]: Forcing deep traversal on source: "Macintosh HD" (mount: '/Volumes/Macintosh HD' fsUUID: 8BC39A4B-5D17-3754-9DFF-1F3E456F4F6F eventDBUUID: C40760ED-0381-432B-B1A6-5FD4ECE25CB6)
04/10/13 17:02:43,472 ReportCrash[3841]: Saved crash report for mds[77] version 707.12 to /Library/Logs/DiagnosticReports/mds_2013-10-04-170243_Mac-Pro-de-jocelyn-fourni er.crash
04/10/13 17:03:02,774 com.apple.backupd[2263]: Backup content size: 93.67 GB excluded items size: 6.66 GB for volume SSD
04/10/13 17:08:09,607 com.apple.backupd[2263]: Backup content size: 450.55 GB excluded items size: 11.96 GB for volume Macintosh HD
04/10/13 17:08:09,623 com.apple.backupd[2263]: Found 5349920 files (525.6 GB) needing backup
04/10/13 17:08:09,624 com.apple.backupd[2263]: 630.72 GB required (including padding), 2 TB available
04/10/13 17:08:09,646 com.apple.backupd[2263]: Waiting for index to be ready (100)
So the backup is now running, and the problem is solved, although I don't really understand what was the problem...
Similar Messages
-
Time machine broken after 10.9.5 update
Time machine will not run after installing 10.9.5. TM was successful 10.9.4 20 minutes before I updated. When TM does a backup, the dialog says "711GB free of 1TB" and "backing up X of 6GB". After a while it says "time machine unexpectedly ran out of disk space" and quits. This happened twice. The third time TM tried to backup, it took 30 minutes to get to "backing up 90K of 6GB", so I gave up.
Anybody else having issues like this?Hey northsidemike,
Thanks for the question and detailed information. I understand that you are experiencing issues creating a Time Machine backup after updating to OS X 10.9.5. The following resource includes multiple links for troubleshooting Time Machine issues. I’ve included a few that are related to your issue:
OS X Mavericks: Time Machine problems
http://support.apple.com/kb/PH14187
Time Machine is slow or seems stuck
If your Time Machine backup disk runs out of space
If Time Machine is slow
If Time Machine remains in the “preparing” stage
Thanks,
Matt M. -
I just got a new MacBook Pro, and I tried to bring across my files from my last mac using time machine. After it was done copying I can't find my files anywhere but the space (about 130gb) has been used on my hard drive. Does anyone know how I can get to them? I did change my user name from 'user' while it was copying, could this have something to do with it?
You don't want to do that by copying.
Your best bet, by far, is to use Setup Assistant. If your Mac is running Snow Leopard, see Using Setup Assistant on Snow Leopard or Leopard.
If it came with Lion, it's a bit different: Using Setup Assistant on Lion -
Time Machine Bug after Restore
Hi all,
I've been learning Time Machine and will share two possible bugs if it is helpful. I am working on a 2011 MacBook Pro, upgraded to Mountain Lion some months back, with 50 GB data on SSD being backed up to and restored from a LaCie SSD 80 GB partition so the speed is very nice: 14 minutes for initial backup and 7 minutes for a Reboot + Command + R restore.
Bug #1. Both (initial) backup and restores begin with large 60 minute estimated times in Time Machine Prefs Progress Bar but, once it gets going, finishes in 14 and 7 minutes respectively. If symptom is due to some quadratic journal searching algorithm, it may explain why APL-CARE warned me about potential 16 hour restores and could be a bug. If it is due to Time Machine just counting what has been transferred so far, then maybe not a bug (but maybe a possible enhancement request).
Bug #2. It appears that the first time Time Machine runs after a Cmd+R restore, it tries to rebuild an entire journal or record of what it has and, if you interrupt this initial backup, you break Time Machine. The next time you try to backup, Time Machine thinks Everything needs to be backed up (even though your disk is identical to what it just restored), and it Fails in my case with message "Time Machine couldn't complete the back to [my LaCie drive because my 50 GB of data is already there and it thinks it needs a full 50 GB more]" in so many words. APL-CARE (and its expert advisor) tried to call this a feature and sent me to your article HT3275 but that seems like a different issue. Since I did not believe Time Machine was so stupid, I ran the sequence again and carefully avoided interrupting Time Machine during its initial backup following my Cmd+R restore and, indeed, it took about 8 minutes to backup 4.5 MB (and rebuild whatever it does that first time). So this feels like a straight-up bug, Time Machine should scare me with a popup if I interrupt it while it is rebuilding its critical list for the first time after a restore. If APL-CARE were correct, it would mean everyone loses all history after a restore, everyone needs to Erase their backup disk and start from scratch, and methinks that too would be a bug.
Hopefully this is helpful, Time Machine is otherwise very cool and I love the Star Trek GUI.
Regards,
Dave.And this is an ERROR in time machine. I just did a test restore again, went quickly, then Time Machine is GONE, GONE, gone trying to restore 5MB, waiting over an hour when a fresh backup takes about 15 minutes.
So only solution is DESTROY all my backups, then start over. Really dumb, and this page has no option to change my post back to a question, also really dumb.
I am going to swear now: cr*p. OK. Fix your **** software please. I'll deal with workarounds till then.
-dave -
Time Machine Backups after recent upgrade to Mountain Lion
Basically to keep a long story short - i need to take my computer in for repair tomorrow. I recently did an upgrade to Mountain Lion a day or two ago. I haven't done a Time Machine backup until today (a couple days after i upgraded to Mountain Lion) because i wanted to make sure that my previous TM backup (Snow Leopard 10.6.8) was the most up to date and best update that i could revert back to if i had any issues with Mountain Lion, or any application compatibility, etc etc.
I don't have any broken applications and it seems like Mountain Lion is running better than Snow Leopard. However, as i said - i'm taking my computer in for repair tomorrow, i would like to know that i have the most up to date Time Machine backup with the new Mountain Lion so that when i restore it back from my Time Machine backup after i get it back from repair, i won't have any issues with the migration, which could potentially lead me into more technicalities.
I have a 500GB Harddrive, with about 70GB left of free space....I did the initial backup prior to upgrading to Mountain Lion, and it upgraded 400+GB of info, now, since Mountain Lion - the first backup with Mountain Lion initially said 46GB - then it went down to 14GB by the time it was all said and done....so what exactly did it back up?
Did it back up all the necessary files to keep Mountain Lion running smoothly when i restore it back to the way it was after i get it back? Did it not back everything up that it needs to? Is it safe to erase my internal drive and do a clean installation so i can take it in, and not worry about not being able to migrate things back over or applications not working correctly?
When i get it back, i presume it will come with Mountain Lion back on it and i can just boot up into the Recovery Disk and restore it from a Time Machine backup that way, correct?
Thanks for the help.
- JasonI received the same error and experienced the same issue that you have described but after performing a Time Capsule soft reset and then toggling the TM Off and then back On I was able issue a backup now and see my previous backups.
Here is the link to where I posted my fix; https://discussions.apple.com/message/19069543#19069543. Someone else had success using a different method. The only comment / complaint that I have since the ML OS X upgrade is that TM now takes at least 20 to 30 seconds before I can click/select a backup.
I hope this helps. -
Time Machine Locked after MacBook Air reformatted. My MacBook Air was overfull due to an Address book issue (duplication) so after many attempts to clear space, I ended up wiping out the system and reloading Lion. This resulted in the Time Machine thinking that it was now connected to a different computer. Apparently this diables the existing information.
Now I can see that the back-ups exist (back to Sept 2012) but they are greyed out, therefore unavailale to restore. Again, this seems like an issue that shouldn't be happening. The whole point of the Time Machine is to enable reinstatement of data after catastrophic failure. What if my computer actually had to be replaced due to a hardware issue? How would I beableto restore anything?
The path already (unsuccessfully) taken;
Open Library on the computer, Open Time Machine, Select Correct date, drill down to correct data you wish to restore, click "Restore".
This did not work because the correct date was greyed out. Restore key was greyed out.Time Machine Locked after MacBook Air reformatted. My MacBook Air was overfull due to an Address book issue (duplication) so after many attempts to clear space, I ended up wiping out the system and reloading Lion. This resulted in the Time Machine thinking that it was now connected to a different computer. Apparently this diables the existing information.
Now I can see that the back-ups exist (back to Sept 2012) but they are greyed out, therefore unavailale to restore. Again, this seems like an issue that shouldn't be happening. The whole point of the Time Machine is to enable reinstatement of data after catastrophic failure. What if my computer actually had to be replaced due to a hardware issue? How would I beableto restore anything?
The path already (unsuccessfully) taken;
Open Library on the computer, Open Time Machine, Select Correct date, drill down to correct data you wish to restore, click "Restore".
This did not work because the correct date was greyed out. Restore key was greyed out. -
I had to restore my iMac from Time Machine. After the restoration all programs are functioning except my Adobe Creative Suite 4 Design Premium. When I start any program in the suite the error message, "Licensing for this product has stopped working." I restarted the computer and tried again to run Photoshop and the same error message appeared. The message was followed by a message that stated that I needed to contact Adobe technical support and mention Error: 150.30. I need Adobe technical support to provide me a solution for my problem so I can continue using my Adobe products installed on my computer.
Unfortunately when Adobe products are restored from backup, especial CS4 and especially Mac, it breaks licensing.
There is a python script included in the license recovery kit that should work if you are familiar with Terminal.
If not, you must reinstall your CS4 suite. You don't need to delete your preferences, so it should be the same as before.
Error "Licensing has stopped working" | Mac OS
Gene -
I was transferring data from my old iMac to my new iMac via Time Machine. After about 4 hours, the electrical power fluctuated and turned off my wi-fi. Now most of my necessary programs are useless. How do I erase that mess and start over?
Hello there, LynnS.
The following Knowledge Base article and it's referenced link should get you started with the Erase and Install of Mavericks:
OS X Mavericks: Erase and reinstall OS X
http://support.apple.com/kb/PH14243
Once you've gone through those 2 articles, this article should help you with restoring from your Time Machine Backup:
OS X Mavericks: Recover your entire system
http://support.apple.com/kb/PH14185
Thanks for reaching out to Apple Support Communities.
Cheers,
Pedro. -
Where do I find the Library in a Time Machine backup after Lion installation?
Where do I find the Library in a Time Machine backp after Lion installation?
You can access the backups of another computer by holding down the option key and selecting "Browse other Time Machine disks" from the Time Machine menu in the menu bar. As for getting to the Library folder, you would have to use something like the free application "Tinker Tool" (not "Tinker Tool System") to make hidden files visible in the Finder, then enter Time Machine.
-
Is it possible to downgrade to mountain lion with the help of a time machine backup after having updated to Mavericks?
Just to be clear, if by downgrade you mean uninstall, then the answer is technically, no.
You can't uninstall an OS. You can erase and re-install the old OS, but if you don't have a prior backup of your data, you'll lose it during the erase procedure. -
Imac keeps crashing in time machine backup after upgrade to mountain lion
2008 imac kept crashing (shutdown and restart) during first backup after upgraded to mountain lion. The backup size was about 10GB but time machine crashed after a while (at most 2GB) and never completed backup. So, I don't have any backup since right before I upgraded from Lion. Any suggestion?
Something strange happened. I was able to get time machine to work by going out to the login screen (the account kept logged in) and let it run the backup with the screen off (screen auto off after a few min). I tried it on two different external drives and that did the trick on both. Since the initial Mountain Lion backup was huge (155 GB), I was quite surprise that it worked at all. I assume your MBP was a Lion to ML. I also just did a 2012 MBP upgrade but that one was smoother. I did not recall having crashing issue. One thing I did find during this was that my WD passport USB drive was corrupted. Not sure it was the cause or not. I had to erase and reformat to get it back to work. Maybe do a verify disk to confirm. Good luck.
-
Why I'm losing space on my internal HD, after i started to use the Time Machine, and after deleting all my files i still dont have any space on my internal HD?
Why I'm losing space on my internal HD, after i started to use the Time Machine, and after deleting all my files i still dont have any space on my internal HD?
-
Time Machine stops after reset in OS X 10.9 ? What is the solution ?
Time Machine stops after reset in OS X 10.9 ? What is the solution ?
Time Machine shows the time of the last backup and it shows a MB-count while backing up.
So it seems to work. Only the Time Machine symbol does not work.
Thanks for your tip.
Greetings, AlbertenHelma -
Time Machine stuck at "Looking for backup disk" after installing Windows 8 via Boot Camp
I've been backing up via Time Machine to an external USB drive and it's been working fine. I recenty installed Windows 8 via Boot Camp and now TM gets stuck forever at "Looking for backup disk...".
I've tried the following, to no avail:
Using "Select Disk" in TM preferences to re-select the disk
Deleting /Library/Preferences/com.apple.TimeMachine.plist
Running system maintenance via Onyx
Resetting PRAM
Formatting the drive and setting it up for TM backups again
The Boot Camp partition is on the same drive as OS X (on a 180GB Intel 330 series SSD). During the Windows installation I re-formatted the partition as NTFS.
If I start OS X in Safe Boot mode, TM backups work. In Safe Boot mode, the NTFS partition isn't loaded so I suspect it has something to do with this. Any ideas would be greatly appreciated.I installed Paragon NTFS for Mac and it started working all of a sudden.
-
Hello!
I have been using Time Machine on the Time Capsule for over a month now and no problems. However when I was installing Lion it had to restart. I did not see that Time Machine was going at the time when I pushed restart until it was too late.
Now Time Machine seems to be stuck on "Preparing Backup" and "Indexing Backups". It has been nearly 20-30 minutes for Indexing and I wonder if I corrupted something or something else. If there a way I can solve this problem? Thanks!I had this same problem, this is going to sound ridiculous but this is what I finally did. I wiped my backup, crazy right?
It's there for when your hard drive crashes, so it's not like you are going to miss much if you wipe it. Tell it to stop backing up, go to disk utility, click your external and then erase it. Go back to time machine settings and reselect it as your backup drive. It will do an initial back up again and you are good to go.
Hope this helps.
Maybe you are looking for
-
Bridge CS6 freezes when generating PDF output (windows 8)
I am using Adobe Bridge CS6 (64bit) on a Windows 8 machine. I have photos that I want to output to PDF. Bridge will freeze in the process of generating the PDF file. I have to go to the Task Manager to quit. Sometimes the PDF file has been made succe
-
Error 500 while deploying Servlets using Weblogic 5.1
hi, i have followed all the intructions on how to run servlets in weblogic 5.1 server. till yesterday i have done nearly 10 servlets which worked perfectly. but today when i coded a new servlet and started runn
-
Hi All, I have seen the settings of OKB9 but not able to understand what Account Assignement category i have to select for different cost elements? Please guide me in understanding the functionality of OKB9 when it is used? Thanks Sonal
-
Ordering Prints from Shutterfly - Blank White Dialog Box
I am trying to order some prints through Photoshop Elements using Shutterfly. I select my prints I want to order, hit order prints from shutterfly. A white dialog box appears overtop of Photoshop elements where I can login to shutterfly. I successful
-
What are best uses for Fireworks?
I've been working with dreamweaver, flash and photoshop for years, but have avoided Fireworks because I could make a nav bar some other way, in flash or just use mouse-overs in Dreamweaver. Now I bought the CS5.5 upgrade and it includes Fireworks whi