10.5.3 and new Time Machine error

[mreg376]

Time Machine (external USB/SATA) on my 2-month old iMac had been working perfectly. I installed 10.5.3. Everything still works perfectly EXCEPT I get an occasional error with Time Machine's hourly backup saying it could not do the backup. I can do the backup manually and the subsequent automatic backup goes OK. It's happened twice since my installation of 10.5.3 last night. I did Repair of the external drive and no problems were found. Any ideas? Thanks.

[Sky Blue]

I've had this too. Never had one error on Time Machine since October, but I had exactly what you described today.

[mreg376]

Originally Posted by Sky Blue

I've had this too. Never had one error on Time Machine since October, but I had exactly what you described today.

Well, now we know it's not us. All we need is a solution...

[todd2000]

I was just about to start a thread on this. It just happened to me. I tried a manual backup, and it was fine, and I assume the next Automated Backup will work if yours did, but what's causing this? Here is the relevant errors from my System Log if someone can get something from it.

May 29 21:41:52 iMac /System/Library/CoreServices/backupd[7740]: Starting standard backup
May 29 21:41:52 iMac /System/Library/CoreServices/backupd[7740]: Backing up to: /Volumes/Backup/Backups.backupdb
May 29 21:41:54 iMac /System/Library/CoreServices/backupd[7740]: No pre-backup thinning needed: 228.9 MB requested (including padding), 118.91 GB available
May 29 21:41:58 iMac /System/Library/CoreServices/backupd[7740]: Stopping backup.
May 29 21:41:58 iMac /System/Library/CoreServices/backupd[7740]: Error: (-43) copying /Users/Todd/Documents/iChats/.DS_Store to /Volumes/Backup/Backups.backupdb/iMac/2008-05-29-214153.inProgress/F1F74F85-52EA-49EF-8373-FD3A9D7E397F/ Macintosh HD/Users/Todd/Documents/iChats
May 29 21:41:58 iMac /System/Library/CoreServices/backupd[7740]: Copied 219 files (40 KB) from volume  Macintosh HD.
May 29 21:41:58 iMac /System/Library/CoreServices/backupd[7740]: Copy stage failed with error:11
May 29 21:42:03 iMac /System/Library/CoreServices/backupd[7740]: Backup failed with error: 11

[davidwarren]

this happened twice today for the first time on my imac at work, the imac at home and my macbook have not done this yet.

[kbmb]

Add me to the list of having this happen exactly as described since installing 10.5.3. I've been running TM on my Mac Pro since Leopard was released without any errors.

I did a manual backup after the error, and that was fine. The next automatic backup has also worked.

Anyone come up with any ideas on why this is happening?

-Kevin

[mreg376]

Originally Posted by kbmb

Add me to the list of having this happen exactly as described since installing 10.5.3. I've been running TM on my Mac Pro since Leopard was released without any errors.

I did a manual backup after the error, and that was fine. The next automatic backup has also worked.

Anyone come up with any ideas on why this is happening?

-Kevin

I was the original poster on this. After it happened twice, I did a Disk Utility "Repair." The repair found nothing wrong with my Time Machine disk, but the error hasn't happened again. Of course it's only been an additional day so I have no idea if it means anything at this point.

[kbmb]

Originally Posted by mreg376

I was the original poster on this. After it happened twice, I did a Disk Utility "Repair." The repair found nothing wrong with my Time Machine disk, but the error hasn't happened again. Of course it's only been an additional day so I have no idea if it means anything at this point.

Just checked my external disk used for TM and everything checks out fine (as well as all internal drives). Let's all keep our eyes open and post back.

-Kevin

[themanfromvlad]

just speculating here, did the people here who are having this issue eject and disconnect their drives before updating? You should always do that before a Mas OS update.

[kbmb]

Originally Posted by themanfromvlad

just speculating here, did the people here who are having this issue eject and disconnect their drives before updating? You should always do that before a Mas OS update.

I did not. The drive was connected during the update. Haven't had an issue before as it's been connected for the .1 and .2 updates.

-Kevin

[mreg376]

Originally Posted by kbmb

Just checked my external disk used for TM and everything checks out fine (as well as all internal drives). Let's all keep our eyes open and post back.

-Kevin

Well, it happened again. So I guess running the general Repair is not the answer.

[apfhex]

I'm having the same problem — only since updating to 10.5.3, same messages in my Console. My Time Machine drive is internal and has been working 100% error free since 10.5.0 until now. Anyone got a clue what's up? Going to try to repair permissions of course and maybe try deleting that pesky .DS_store file.

5/31/08 1:52:21 AM /System/Library/CoreServices/backupd[9817] Backing up to: /Volumes/FTL/Backups.backupdb 
5/31/08 1:52:24 AM /System/Library/CoreServices/backupd[9817] No pre-backup thinning needed: 158.9 MB requested (including padding), 338.71 GB available 
5/31/08 1:52:24 AM /System/Library/CoreServices/backupd[9817] Stopping backup. 
5/31/08 1:52:24 AM /System/Library/CoreServices/backupd[9817] Error: (-43) copying /Applications/.DS_Store to /Volumes/FTL/Backups.backupdb/Battlestar/2008-05-31-015221.inProgress/69BC6A7D-3E7B-4B5D-94AC-6BA82FA1BE8C/Galactica/Applications 
5/31/08 1:52:24 AM /System/Library/CoreServices/backupd[9817] Copied 0 files (0 bytes) from volume Galactica. 
5/31/08 1:52:24 AM /System/Library/CoreServices/backupd[9817] Copy stage failed with error:11 
5/31/08 1:52:30 AM /System/Library/CoreServices/backupd[9817] Backup failed with error: 11

[kbmb]

Originally Posted by apfhex

I'm having the same problem — only since updating to 10.5.3, same messages in my Console. My Time Machine drive is internal and has been working 100% error free since 10.5.0 until now. Anyone got a clue what's up? Going to try to repair permissions of course and maybe try deleting that pesky .DS_store file.

My error didn't occur with the .DS_STORE file for what it's worth.

May 30 19:10:37 /System/Library/CoreServices/backupd[10429]: Starting standard backup
May 30 19:10:37 /System/Library/CoreServices/backupd[10429]: Backing up to: /Volumes/MacBackup/Backups.backupdb
May 30 19:10:38 /System/Library/CoreServices/backupd[10429]: No pre-backup thinning needed: 1.34 GB requested (including padding), 319.31 GB available
May 30 19:10:39 /System/Library/CoreServices/backupd[10429]: Stopping backup.
May 30 19:10:39 /System/Library/CoreServices/backupd[10429]: Error: (-43) copying /Library/Printers/Brother to /Volumes/MacBackup/Backups.backupdb/buzzlightyear/2008-05-30-191037.inProgress/99E2A133-EF6E-45D3-896F-ED929A859F89/MacHD/Library/Printers
May 30 19:10:39 /System/Library/CoreServices/backupd[10429]: Copied 72 files (186 bytes) from volume MacHD.
May 30 19:10:39 /System/Library/CoreServices/backupd[10429]: Copy stage failed with error:11
May 30 19:10:44 /System/Library/CoreServices/backupd[10429]: Backup failed with error: 11

-Kevin

[apfhex]

I noticed, it seems to be a random file, and the error probably has nothing specific to do with the file listed in the Console, but I thought it couldn't hurt to delete a DS_store file. The first time I got the error it was from a file in /private/etc/.

[mreg376]

Still happening. This morning I awoke to the error message, and noted that the hourly backup that should have occurred at 4:10 am did not. But the subsequent backups were done. Very strange...

[davidwarren]

it hasn't happened to me after the first two times...

[Silver-Fox]

I got this once, but havent again

[Sky Blue]

Originally Posted by Silver-Fox

I got this once, but havent again

Yeah, I've had it once, as noted above, but it's been fine since.

[mreg376]

Originally Posted by Sky Blue

Yeah, I've had it once, as noted above, but it's been fine since.

I'm not that lucky. It's been happening about once a day. I'm not that concerned about the backup, since in each case the subsequent automatic backups were fine. But I'm afraid of what it might bode in the event I have to do a major restore.

[kbmb]

Originally Posted by mreg376

I'm not that lucky. It's been happening about once a day. I'm not that concerned about the backup, since in each case the subsequent automatic backups were fine. But I'm afraid of what it might bode in the event I have to do a major restore.

Have you tried turning TM off. Unmounting the drive, reboot, the drive should remount on the next boot, and then turning TM back on?

Never tried this myself, just giving a suggestion to get your error to stop.

You drive doesn't power itself down does it? Did any energy saver settings change?

Just wondering if something else changed in your setup to cause this.

-Kevin

[mreg376]

Originally Posted by kbmb

Have you tried turning TM off. Unmounting the drive, reboot, the drive should remount on the next boot, and then turning TM back on?

Never tried this myself, just giving a suggestion to get your error to stop.

You drive doesn't power itself down does it? Did any energy saver settings change?

Just wondering if something else changed in your setup to cause this.

-Kevin

No, no other changes other than 10.5.3, and the external drive does not power down. The odd thing is that it only happens occasionally. But I will try your suggestion about unmounting and rebooting.

[MacForMeOneDay]

Originally Posted by Sky Blue

Yeah, I've had it once, as noted above, but it's been fine since.

I too had the error(2 times in 2 days), did the Disk Repair on the TM drive (Firewire 800 External).
It hasn't happened since for me either.

[kbmb]

Just had it occur for the 2nd time since 10.5.3. Next backup was fine.

Previously I have verified all internal disks, as well as the TM external drive. Everything checked out fine.

This is clearly a 10.5.3 issue. C'mon Apple.

-Kevin

[bigjnyc]

i havent been able to back up at all, keep getting the error message and i've tried all suggestions. its getting pretty annoying as i've added alot of important files that i would like backed up. I hope someone figures out a fix or apple addresses the issue soon.

fyi im using WD 250GB connected via airport extreme.

[MacForMeOneDay]

Originally Posted by MacForMeOneDay

I too had the error(2 times in 2 days), did the Disk Repair on the TM drive (Firewire 800 External).
It hasn't happened since for me either.

My TM error came back today. Even a manual "Backup Now" failed.