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

Is anyone else having issues with time machine after the 10.5.7 update

Basically my time machine wont back up anything anymore I have no idea why but it was the result of the update any ideas?

15 Macbook Pro, Mac OS X (10.5.6)

Posted on May 13, 2009 8:48 AM

Reply
18 replies

May 13, 2009 9:19 AM in response to chris.panagop

I'm having problems. I have a Time Capsule and after updating to 10.5.7 it doesn't recognize my Time Machine backup disk (though I can see the disk in the Finder). The Time Machine menu bar icon says 'Time Machine not configured' and when I go to Time Machine preferences, there is no way I can add my Time Capsule disk as the location for Time Machine.

Ironically, I made sure everything was backed up with Time Machine prior to the 10.5.7 update, only now I can't access it. Maybe I could expand the sparse image from the Finder, but I don't want to do a full restore.

May 13, 2009 10:07 AM in response to Allan Eckert

Starting standard backup
Mounted network destination using URL: afp://Chris%20Panagopoulos@Chris-Panagopouloss-Time-Capsule.local/Chris%20Panag opoulos's%20Time%20
Backup destination mounted at path: /Volumes/Chris Panagopoulos's Time
Disk image /Volumes/Chris Panagopoulos's Time /Chris Panagopoulos’s MacBook Pro_0023df7c95ae.sparsebundle mounted at: /Volumes/Backup of Chris Panagopoulos’s MacBook Pro
Backing up to: /Volumes/Backup of Chris Panagopoulos’s MacBook Pro/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
Backup canceled.
Ejected Time Machine disk image.
Ejected Time Machine network volume.

I canceled the backup after about 20 min of "preparing" the backup

May 13, 2009 3:33 PM in response to chris.panagop

chris.panagop wrote:

Event store UUIDs don't match for volume: Macintosh HD


This means that TM can't be sure that what's on the disk matches it's records. The most common cause is an abnormal shutdown, but in the case of a system upgrade, it's probably just the large volume of changes (10.5.6 updated about *ten thousand* files, as I recall). This overwhelms the log of changes that OSX keeps on each drive.

Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|


Because of the UUID problem, this means TM must examine every file and folder on your system to see what's changed and needs to be backed-up. Obviously a lengthy procedure.

And, after an upgrade, there will obviously be a large number (if not size) of files to back up, so that will take a while, too. Just let it run.

May 18, 2009 6:55 AM in response to chris.panagop

Hi !

So, having Problems too. After udating from 10.5.6 to 10.5.7, TimeMachine wasn´t able to reach my Disk at my Airport Extreme.

Formated the Disk, and took a new backup under 10.5.7 -> ok
Now TimeMachine tells me, it can´t copy the daily backup to Disk.

That´s what TimeMachineBuddy says

Starting standard backup
Mounted network destination using URL: afp://Thorsten%20Seifert@Airport%2025. afpovertcp.tcp.local/TM320GB
Backup destination mounted at path: /Volumes/TM320GB-1
Disk image /Volumes/TM320GB-1/MacBook_001b63ba9975.sparsebundle mounted at: /Volumes/Backup of MacBook
Backing up to: /Volumes/Backup of MacBook/Backups.backupdb
Event store UUIDs don't match for volume: MacBook
No pre-backup thinning needed: 12.64 GB requested (including padding), 136.84 GB available
Waiting for index to be ready (906 > 0)
Error: (-36) SrcErr:YES Copying /usr/bin/smbget to (null)
Error: (-36) SrcErr:YES Copying /usr/bin/smbpasswd to (null)
Error: (-36) SrcErr:NO Copying /usr/bin/smbget to /Volumes/Backup of MacBook/Backups.backupdb/MacBook/2009-05-15-151128.inProgress/740E0913-A69C-440 F-928B-E45F1BAF6E7F/MacBook/usr/bin
Stopping backup.
Error: (-8062) SrcErr:NO Copying /usr/bin/smbget to /Volumes/Backup of MacBook/Backups.backupdb/MacBook/2009-05-15-151128.inProgress/740E0913-A69C-440 F-928B-E45F1BAF6E7F/MacBook/usr/bin
Copied 184 files (3.6 MB) from volume MacBook.
Copy stage failed with error:11
Backup failed with error: 11
Ejected Time Machine disk image.
Ejected Time Machine network volume.


So, please help.
Bye

May 18, 2009 9:41 AM in response to trefies

trefies wrote:

Error: (-36) SrcErr:NO Copying /usr/bin/smbget


That's part of your OS; a Unix executable file.

You may have a problem on your internal HD. Use Disk Utility (in your Applications/Utilities folder) to run a +Verify Disk+ (not permissions) on your internal HD. If it reports errors, you'll have to boot from your Leopard Install disc and use it's copy of DU to fix them. Post back if you need to do this but don't know how.

If that reports no errors, exclude your TM disk from any anti-virus scanning.

Also exclude it from Spotlight, via System Preferences > Spotlight > Privacy.

Then try a +Back Up Now.+

May 18, 2009 10:53 AM in response to trefies

There seem to be a slew of 10.5.7 defects related to Time Machine. I had a PERFECT system, where I was using file sharing on a G5 to mount an external drive, and four other Macs backing up to the same Time Machine drive. It worked flawlessly -- even running 10.5.7 on the remote macs.

But once I changed the HOST over to 10.5.7 -- none of the remote Macs can mount the Host's shared drive.

I guess we will need to await someone from Apple to post some guidance on this -- or wait until someone with Time Machine guru credentials runs into the same problem and posts a fix.

Stephen

Is anyone else having issues with time machine after the 10.5.7 update

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