Topic : Time Machine WON'T BACKUP with new 10.5.2 update.

Topic Archived This topic has been archived - replies are not allowed.


This question is not answered. "Helpful" answers available: 2 . "Solved" answers available: 1 .



            Permlink
            Replies : 33 - Pages : 3 [ 1 2 3 | Next ] - Last Post : Feb 16, 2008 1:57 PM by: Aaron Hung
The Kevon

Posts: 1
From: California
Registered: Feb 12, 2008
Time Machine WON'T BACKUP with new 10.5.2 update.
Posted: Feb 12, 2008 9:56 AM
 

I just updated my MacBook with the 10.5.2 update, and since then, my 500 GB MyBook and Time Machine aren't agreeing with each other. Whenever a Time Machine begins, it'll go though 1/6th of backing up the data and up comes a message saying "Unable to complete back up. An error occurred while copying files to the back up volume." and that's it. I've retried numerous times to back up my data but the same message keeps coming up.

What does that mean??

MacBook      
demiller

Posts: 5
From: Indianapolis, IN
Registered: Feb 12, 2008
Re: Time Machine WON'T BACKUP with new 10.5.2 update.
Posted: Feb 12, 2008 10:02 AM   in response to: The Kevon
 

Don't have an answer to this, but I'm seeing the same exact issue. I can restore files from the MyBook, but my backups fail the same way. Disk Utility is reporting no problems with the disk.

MacBook Pro 17"   Mac OS X (10.5.1)   Actually 10.5.2  
AuroraProject


Posts: 115
Registered: Sep 18, 2006
Re: Time Machine WON'T BACKUP with new 10.5.2 update.
Posted: Feb 12, 2008 10:04 AM   in response to: The Kevon
 

I just completed a Time Machine backup with no issues, updated to 10.5.2 last night. I'm running an old ide hard drive on a ide to usb bridge for my backup drive. Not pretty to look at, but it gets the job done.

MacBook Pro 17" 2.16ghz Core Duo, 2gigs RAM, 120gig HDD   Mac OS X (10.5.1)    
Aaron Hung

Posts: 52
Registered: Dec 6, 2007
Re: Time Machine WON'T BACKUP with new 10.5.2 update.
Posted: Feb 12, 2008 10:55 AM   in response to: demiller
 

I'm having the same problem. I see others (in other threads) are reporting the same. I ran disk utility's verify permissions thing and it still hasn't worked. Um...now what?

FYI: From Console utility, I get this:

Feb 12 13:20:00 aaron-macbook-pro kernel[0]:
Feb 12 13:20:00 aaron-macbook-pro /System/Library/CoreServices/backupd133: Copied 20702 files (1.1 GB) from volume My Mac.
Feb 12 13:20:00 aaron-macbook-pro /System/Library/CoreServices/backupd133: Copy stage failed with error:11
Feb 12 13:20:04 aaron-macbook-pro /System/Library/CoreServices/backupd133: Backup failed with error: 11

I did these using "Backup Now" so I'm going to let it do it automatically. From what others are saying, this isn't the problem, it's something else.

Message was edited by: Aaron Hung

MacBook Pro   Mac OS X (10.5.1)   2.5 GHz 4GB 667 MHz SDRAM  
Eelco Vriezekolk

Posts: 6
Registered: Jul 6, 2003
Re: Time Machine WON'T BACKUP with new 10.5.2 update.
Posted: Feb 12, 2008 12:32 PM   in response to: The Kevon
 

Same issues here. Other forum posts suggested to check for a "backup in progress" file left over from a previous (failed) backup. This should be in your machine's folder on the Time Machine drive. I had one, deleted it, and then manually started a backup. Went fine. This solved the problem for me.

iMac   Mac OS X (10.5.1)    
Aaron Hung

Posts: 52
Registered: Dec 6, 2007
Re: Time Machine WON'T BACKUP with new 10.5.2 update.
Posted: Feb 12, 2008 12:34 PM   in response to: Aaron Hung
 

I kinda resolved this. I went into Console utility again and noticed that it was stuck on a video file (file #13 in a lecture series), so I deleted the file and see if it would backup. Then it gets stuck on #14. I've had these files on my laptop for a while, so I went into previous TM backups to see, and saw that it never backed up past file #12; it just skipped over them. Only after the update, it gave an error message. So, I deleted all files after #12 and tried backing up again, and it went fine.

I guess it's nice to get an error message so you know what files aren't being backed up. Anyway, give it a try and see if it works for you.

MacBook Pro   Mac OS X (10.5.1)   2.5 GHz 4GB 667 MHz SDRAM  
demiller

Posts: 5
From: Indianapolis, IN
Registered: Feb 12, 2008
Re: Time Machine WON'T BACKUP with new 10.5.2 update.
Posted: Feb 12, 2008 12:51 PM   in response to: Eelco Vriezekolk
 

I didn't have a "Backup in progress file" but I did dig around in the system log and found an error message indicating the the backup was failing on a specific folder. Doing a little Googling I found:

http://discussions.apple.com/thread.jspa?messageID=6558547

Which suggests excluding the folder in question from the backup and trying again. Since this was just a folder of Red vs. Blue movies I'd downloaded several years ago I just tossed it, and executed a manual backup. The "Preparing..." phase ran a long time, as did the "Finishing Backup..." phase, but eventually it completed successfully. THat may have been what removed the "backup in progress" file, I didn't check until the backup was done.

I've no idea why that folder, which had been backed up successfully before, suddenly was offensive to Time Machine. Removing it seems to have done the trick, though.

MacBook Pro 17"   Mac OS X (10.5.1)    
demiller

Posts: 5
From: Indianapolis, IN
Registered: Feb 12, 2008
Re: Time Machine WON'T BACKUP with new 10.5.2 update.
Posted: Feb 12, 2008 1:35 PM   in response to: Aaron Hung
 

I can confirm Aaron's findings. It was one particular video file that was causing the issue on my system, and in checking past backups, this file had never been backed up. The failed backups were also creating ".inprogress" files in the current backup folder.

I also found messages like this in system.log:

/System/Library/CoreServices/backupd4216: Event store UUIDs don't match for volume: Macintosh HD

However, once I got a successful backup these went away. I've had several successful, and quick backups since I deleted the problem file.

MacBook Pro 17"   Mac OS X (10.5.2)    
HanselJr


Posts: 121
Registered: Jul 4, 2007
Re: Time Machine WON'T BACKUP with new 10.5.2 update.
Posted: Feb 12, 2008 1:36 PM   in response to: The Kevon
 

I'm glad i did not update!!!. same thing happened to me, when 1.5.1 came out... i had to send my Mac Pro over to the Apple Store, because the only way to restore my comp was by using Apples booting Hard Drive and re-installing all my apps back again..

Mac Pro, Sonnet Tempo SATA e2P, ATI Radeon X1900 XT 512MB, eSATA HD Seagate300GB   Mac OS X (10.5)   Leopard  
scottyoTokyo

Posts: 7
From: Japan
Registered: Feb 12, 2008
Re: Time Machine WON'T BACKUP with new 10.5.2 update.
Posted: Feb 12, 2008 3:54 PM   in response to: Aaron Hung
 

I also see TM failures in 10.5.2, with a specific file that is the last one attempted, leaving only an inProgress bundle on backup volume.

Story: was getting corruption on boot drive per DiskUtil, so Repaired boot drive and Archive and Installed 10.5.1 using Tokyo Ginza Store's Genius Bar hand-burned loaner 10.5.1 DVD (can't find mine). At home, checked my TM volume, it also had corruption, but DiskUtil failed to repair, and a following repair run found different errors, plus made it unmountable. TM volume is on a 500GB ATA drive in a 4-bay enclosure connected by USB 2; this appears to have been highly reliable since Nov when I set it up; I suspect the corruption is consequent to boot volume corruption, since boot volume appears to have failed to store some iCal appointments, etc, indicating consequential damage.

Boot drive still good, so I Erased TM volume with DiskUtil, putting journalled HFS+ (default) filesys on it. But now initial copy to TM volume fails part way through, at about 5GB of about 55GB, failing on an alias file in iWork/Pages, on a .nib deep down, seen below:

<irrelevant stuff snipped except line preceding first error>:

2/12/08 21:45:25 /System/Library/CoreServices/backupd4077 No pre-backup thinning needed: 5.07 GB requested (including padding), 373.21 GB available
2/12/08 21:52:00 /System/Library/CoreServices/backupd4077 Error: (-48) copying /Applications/iWork '08/Pages.app/Contents/Frameworks/SFInspectors.framework/Versions/A/Resources/French.lproj/SFIFillSubInspector.nib/keyedobjects.nib to /Applications/iWork '08/Pages.app/Contents/Frameworks/SFInspectors.framework/Versions/A/Resources/French.lproj/SFIFillSubInspector.nib
2/12/08 21:52:00 /System/Library/CoreServices/backupd4077 Error: (-48) copying /Applications/iWork '08/Pages.app/Contents/Frameworks/SFInspectors.framework/Versions/A/Resources/French.lproj/SFIFormatBarColorMenu.nib/keyedobjects.nib to /Applications/iWork '08/Pages.app/Contents/Frameworks/SFInspectors.framework/Versions/A/Resources/French.lproj/SFIFormatBarColorMenu.nib

<many similar messages before abort>

I tracked down in detail another error in the copying of iWeb, which was the last thing found in the inProgress package, and was incomplete. The error manifests deep in the Russian localization at Resources/ru.lproj/Templates/About Me/. An alias, Baby_Image5.jpg, to Resources/Shared/Image5.jpg, is 0-length on TM volume (all aliases in that dir on TM volume are dangling, since Resources/Shared has not yet been copied), where all preceding copied aliases are 4K allocations with 50-60 bytes in them, and boot drive version of the alias is also non-0. Can't find a util that will hexdump contents of a dangling alias :-(

Finally, the TM volume can't be umounted (I relaunched Finder just in case, and System Preferences and backupd not currently running, fuser shows no one has it open) so I'll have to pull the plug, reboot for safety, and start from scratch with a full Diskutil zero-fill erase of TM volume.

Am taking my MacBook to Canada next week to fix my Dad's networking (he also has MacBook) which has been broken for months, and would love to have a secure TM backup before I go...

MacBook   Mac OS X (10.5.2)   2GB, 160GB boot, 500GB Time Machine on USB  
rogerjth

Posts: 201
From: USA
Registered: Jul 30, 2007
Re: Time Machine WON'T BACKUP with new 10.5.2 update.
Posted: Feb 13, 2008 2:59 PM   in response to: Aaron Hung
 

"kinda resolved this. I went into Console utility again and noticed that it was stuck on a video file (file #13 in a lecture series), so I deleted the file and see if it would backup. Then it gets stuck on #14"

Aaron, I am curious (since I am experiencing similar pbs as exposed here!): WHICH area of the Console (logs?) do you go to to get such detailed info about "stuck" files??? I have looked up logs, followed failed backups (accompanied with drive thrashing - very worrisome!!) and I have NOT noticed such specific info about backups.

Thanks!

  • Roger T


MacBookPro 17" - 2.4ghz   Mac OS X (10.5.2)   MacOS X/WinXP via BootCamp - Mixed Mac/Win networks - iPhone 8gb - G-Drive 500gb  
Aaron Hung

Posts: 52
Registered: Dec 6, 2007
Re: Time Machine WON'T BACKUP with new 10.5.2 update.
Posted: Feb 13, 2008 3:09 PM   in response to: rogerjth
 

This was under "system.log" (under LOG FILES)

MacBook Pro   Mac OS X (10.5.1)   2.4 GHz 4GB 667 MHz SDRAM  
2baa

Posts: 6
From: NW Georgia
Registered: Jan 11, 2006
Re: Time Machine WON'T BACKUP with new 10.5.2 update.
Posted: Feb 13, 2008 7:46 PM   in response to: The Kevon
 

I just upgraded to 10.5.1 last week. Time machine took forever to back up and would lock up my system during backups for about a day. After that it was as smooth as silk.

Then I did the initial 10.5.2 Time Machine backup, and it wouldn't get more than 700MB into a 143GB backup before refusing to go an inch further. It would hang up ALL finder operations for several minutes at a time, let me do a couple of clicks, and then hang again. Looking at top and Application Monitor let me see that Time Machine would go inactive for minutes at a time, come back to life, and then go inactive again.

I finally checked the system log and found up that it was hanging up and failing on one particular directory that evidently had a lot of file corruption (in this case, World Book 2006 .mov files). I removed the directory, repaired permissions, checked the volume, and it's chugging away slowly (still doing a new first backup; I partitioned the drive again), but consistently, with no hangups.

So let me suggest that you go to Console, check the system logs while TM's running, and see if Time Machine consistently hangs up in particular directories or applications. If it is, and if the problem content can be removed and replaced later, try it.

iMac G5 iSight   Mac OS X (10.5.2)    
rogerjth

Posts: 201
From: USA
Registered: Jul 30, 2007
Re: Time Machine WON'T BACKUP with new 10.5.2 update.
Posted: Feb 14, 2008 12:43 AM   in response to: Aaron Hung
 

+This was under "system.log" (under LOG FILES+)

Thanks, Aaron.
I'll have to keep an eye on this file next time backup flames out again!
Seems that the logs sort of "renew" themselves periodically in that older items disappear from them?

  • rt


MacBookPro 17" - 2.4ghz   Mac OS X (10.5.2)   MacOS X/WinXP via BootCamp - Mixed Mac/Win networks - iPhone 8gb - G-Drive 500gb  
Aaron Hung

Posts: 52
Registered: Dec 6, 2007
Re: Time Machine WON'T BACKUP with new 10.5.2 update.
Posted: Feb 14, 2008 1:43 AM   in response to: rogerjth
 

Yeah, I'm not entirely sure whether they delete them when you reboot, or at the start of a new day.

Quick note, btw. I had another TM failure. I went into Console log files again and saw that it had something to do with iTunes. It didn't say which file in particular, so I excluded iTunes from the backup, and then it backed up file. When I tried opening iTunes, it did something bizarre. It had deleted my entire library and was trying to import it again (you know, determine gapless information, etc.) So, I stopped it, then when to my older TM backups to restore the library. Then, I removed iTunes from my excluded files and tried backing it up again. It seems to have worked. It tried to backup 16 GB (I went to sleep and just woke up) and from what I can see, it didn't get an error.

I'm beginning to wonder if the new TM update is causing some unusual conflicts with iTunes. I don't know if anyone else had this problem.

Whoever allowed this latest update to go out should really be fired. It seems to have created problems for many people who didn't have problems before.

MacBook Pro   Mac OS X (10.5.1)   2.4 GHz 4GB 667 MHz SDRAM