Time Machine Failure (log provided)

dmetzcher

dmetzcher

Metzcher.com
Time Machine stopped backing up two days ago in the middle of the day. The error is the same just about every time. I've repaired permissions, deleted .inProgress files, updated the OS to the latest release, applied all security patches, etc. I've spent three hours working on this, and need some advice.

The log information is below. I'm running a Mac Pro with two 500GB internal drives. One is the Time Machine drive. I've had issues with backups once or twice in the past, but deleting the .inProgress backup files has solved them.

This is the error. It's something with an iPhoto theme, which is weird, since iPhoto hasn't changed since I installed iLife '08 many, many months ago.

10/26/08 4:03:52 AM /System/Library/CoreServices/backupd[900] Error: (-43) SrcErr:NO Copying /Library/Application Support/iPhoto/Themes/Doodle-FoldedCard-V.IPBookTheme/Contents/Resources/themeIcon.tiff to /Volumes/Time Machine/Backups.backupdb/Mac Pro/2008-10-26-031945.inProgress/B61239F0-4723-47E1-8D1E-C724783986E7/Macintosh HD/Library/Application Support/iPhoto/Themes/Doodle-FoldedCard-V.IPBookTheme/Contents/Resources
Click to expand...

Please help. Thanks. :)

Here is the whole log...
===============================================
10/26/08 3:19:44 AM /System/Library/CoreServices/backupd[900] Backup requested by user
10/26/08 3:19:44 AM /System/Library/CoreServices/backupd[900] Starting standard backup
10/26/08 3:19:44 AM /System/Library/CoreServices/backupd[900] Backing up to: /Volumes/Time Machine/Backups.backupdb
10/26/08 3:19:45 AM /System/Library/CoreServices/backupd[900] Event store UUIDs don't match for volume: Macintosh HD
10/26/08 3:19:45 AM /System/Library/CoreServices/backupd[900] Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
10/26/08 3:48:34 AM /System/Library/CoreServices/backupd[900] Starting pre-backup thinning: 3.04 GB requested (including padding), 2.60 GB available
10/26/08 3:50:02 AM /System/Library/CoreServices/backupd[900] Deleted backup /Volumes/Time Machine/Backups.backupdb/Mac Pro/2008-09-26-010753: 2.67 GB now available
10/26/08 3:50:16 AM /System/Library/CoreServices/backupd[900] Deleted backup /Volumes/Time Machine/Backups.backupdb/Mac Pro/2008-10-24-234543: 2.67 GB now available
10/26/08 3:50:23 AM /System/Library/CoreServices/backupd[900] Deleted backup /Volumes/Time Machine/Backups.backupdb/Mac Pro/2008-10-24-224441: 2.67 GB now available
10/26/08 3:50:30 AM /System/Library/CoreServices/backupd[900] Deleted backup /Volumes/Time Machine/Backups.backupdb/Mac Pro/2008-10-24-214449: 2.68 GB now available
10/26/08 3:50:42 AM /System/Library/CoreServices/backupd[900] Deleted backup /Volumes/Time Machine/Backups.backupdb/Mac Pro/2008-10-24-204447: 2.83 GB now available
10/26/08 3:50:51 AM /System/Library/CoreServices/backupd[900] Deleted backup /Volumes/Time Machine/Backups.backupdb/Mac Pro/2008-10-24-194528: 2.83 GB now available
10/26/08 3:51:22 AM /System/Library/CoreServices/backupd[900] Deleted backup /Volumes/Time Machine/Backups.backupdb/Mac Pro/2008-10-25-034703: 2.84 GB now available
10/26/08 3:51:36 AM /System/Library/CoreServices/backupd[900] Deleted backup /Volumes/Time Machine/Backups.backupdb/Mac Pro/2008-10-25-031035: 2.85 GB now available
10/26/08 3:51:50 AM /System/Library/CoreServices/backupd[900] Deleted backup /Volumes/Time Machine/Backups.backupdb/Mac Pro/2008-10-25-014534: 2.86 GB now available
10/26/08 3:51:50 AM /System/Library/CoreServices/backupd[900] Removed all 9 expired backups, more space is needed - deleting oldest backups to make room
10/26/08 3:59:00 AM /System/Library/CoreServices/backupd[900] Deleted backup /Volumes/Time Machine/Backups.backupdb/Mac Pro/2008-06-20-092030: 21.97 GB now available
10/26/08 3:59:00 AM /System/Library/CoreServices/backupd[900] Pre-backup thinning completed successfully: 10 backups were deleted
10/26/08 3:59:00 AM /System/Library/CoreServices/backupd[900] Backup date range was shortened: oldest backup is now Jun 27, 2008
10/26/08 4:03:51 AM /System/Library/CoreServices/backupd[900] Stopping backup.
10/26/08 4:03:52 AM /System/Library/CoreServices/backupd[900] Error: (-43) SrcErr:NO Copying /Library/Application Support/iPhoto/Themes/Doodle-FoldedCard-V.IPBookTheme/Contents/Resources/themeIcon.tiff to /Volumes/Time Machine/Backups.backupdb/Mac Pro/2008-10-26-031945.inProgress/B61239F0-4723-47E1-8D1E-C724783986E7/Macintosh HD/Library/Application Support/iPhoto/Themes/Doodle-FoldedCard-V.IPBookTheme/Contents/Resources
10/26/08 4:03:52 AM /System/Library/CoreServices/backupd[900] Copied 403 files (120.8 MB) from volume Macintosh HD.
10/26/08 4:03:52 AM /System/Library/CoreServices/backupd[900] Copy stage failed with error:11
10/26/08 4:03:59 AM /System/Library/CoreServices/backupd[900] Backup failed with error: 11
===============================================
 
Well to fix a time machine disk you must connect to it via wired connection. Then you can use /Applications/Utilities/Disk Utility and 'repair the disk or use your favorite disk reap program (Disk Warrior, Drive 10, etc.). Hopefully this will fix it.
 
Satcomer said:
Well to fix a time machine disk you must connect to it via wired connection. Then you can use /Applications/Utilities/Disk Utility and 'repair the disk or use your favorite disk reap program (Disk Warrior, Drive 10, etc.). Hopefully this will fix it.
Click to expand...

I'll try this now with Disk Utility. If I verify the disk, and it says all good, can I skip the repair, or should I still run it?
 
Last edited:
Verify Disk failed. Trying a repair now.
If the repair fails...do I need to erase it and start over with my Time Machine backups?

Verifying volume “Time Machine”
Checking Journaled HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Invalid node structure
Volume check failed.

Error: Filesystem verify or repair failed.
Click to expand...

(I'm starting to get a little worried...backups are all that separate us from the lower primates.)
 
And here are the Disk Utility messages when I ran a repair on the Time Macine volume.

Verify and Repair volume “Time Machine”
Checking Journaled HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Invalid node structure
Volume check failed.

Error: Filesystem verify or repair failed.
Click to expand...

OK, so should I wipe the Time Machine disk and try to start over with it?
What does this all mean about the TM disk itself. Is it physically damaged in some way, or is this not an indication of that?
 
I rebooted. OS X is telling me that I should reformat the Time Machine disk ASAP. I cannot even repair the disk any longer.

So I guess the main question now is should I even use this disk any longer?
If this is a hardware issue (could it be?), should I use another available internal disk instead? I have another one that I haven't even written to in about a year. I used to use it for cloning my startup disk before I got Leopard.

Or, if I should reformat and go through the long initial TM backup, I'll do that.

Just looking for advice on which route is my best option right now.

Thanks.
 
. . . anyways, do you NEED to save the data on the TM drive? If you already have the data, what you propose may be the easiest thing.

Otherwise, I would consider a better disk repair program such as Disk Warrior. With that one in particular you can take a "picture" of your drive and try to pull files if it does not repair it.

--J.D.
 
Doctor X said:
. . . anyways, do you NEED to save the data on the TM drive? If you already have the data, what you propose may be the easiest thing.

Otherwise, I would consider a better disk repair program such as Disk Warrior. With that one in particular you can take a "picture" of your drive and try to pull files if it does not repair it.

--J.D.
Click to expand...

I don't really need anything off the Time Machine disk since it's just a backup of my startup disk. Of course, the hours I'll need to spend waiting for TM to do its thing after I erase the disk is going to be irritating, but stuff happens. My main question is whether or not I should erase the TM disk and tell TM to use it again, or if the disk is physically damaged and I should just scrap it altogether.

I've erased the disk. I ran a disk repair on the erased disk (there's nothing on it right now, so I'd expect to see what I did see, posted below).
Verify and Repair volume “Time Machine”
Checking Journaled HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
Checking volume information.
The volume Time Machine appears to be OK.
Click to expand...

Now I'm going to tell TM to use the disk again.

Assuming there is no physical issue with the disk...why did this happen? What have I been seeing here...is this just corruption that sometimes happens? Am I likely to see it again, or is it just bad luck?

I really should invest in DiskWarrior or [another more robust disk utility], but is Mac OS X able to tell me if there are physical issues with the disk itself, or do I have to buy a specialized utility for that?

Thanks.
 
Hrrrrrrm . . . to my knowledge--and I immediately defer to Gurus--Disk Utility does not do a surface scan of the HD to check for/isolate bad blocks. It may. It may do it as part of that snazzy hardware check that takes a night to run. I have never done it.

I am assuming your HD has "SMART" ability? This should, hopefully, tell you if you are having problems with your HD. Of course . . . I have not had an HD failure on a disk that IS "SMART," so take that with a big scoop of salt.

Disk Warrior is a good investment in my opinion of "finding" data. However, since you DO back up disks it may not be as critical. TechTools is good at fixing things AND can do a surface scan on your HD.

Do you need either of those? I defer to the Gurus, but in my limited experience failing HDs, they fail. They may "cough" or "burb" a bit, but then they go. All of the HDs that have died on my--internal HDs of various Powerbooks--DIED.

Save one. Coincidentally, a student told me he had spent the night after a HD failure on a PC. I let him hit me as I asked that annoying question: "Did you back up your data?"

That night, something that ran in the background crashed--on OS 9. As I pulled out my diagnosis disks . . . I thought . . . okay . . . grabbed a bunch of CDs and spent an hour burning critical stuff.

Then I tried to fix . . . DOOM! Now I cannot boot off the drive.

Now, DiskWarrior was able to "take a picture" of the drive, so I could still pull data off if I needed.

I happen to have both since I could get them paid for :). Do you NEED such both of such utilities? In my uneducated opinion, DW will fix volumes and find data during a disaster. For fixing permissions and the like, I trust the free Onyx--which is faster--or Cocktail--which is shareware. It does not seem to do as good of a job repairing files like TT.

TT can check things on your computer. You can also make a small "bootable" partition. Critics scoff at this, but that has saved my ass when I have done something really stupid. Its diagnostics are not full-proof with failing RAM. It seems to "upgrade" volumes as well as DW. It can also defrag your HD which, as a thread HERE discusses, may really not be all that bloody necessary in 10.4-10.5+

But . . . it cannot take a "picture" of your HD.

Hope that helps. More to your question: if you have your data backed up, the WORSE that can happen is you discover your drive IS dying and it . . . dies. Then you got to replace it.

--J.D.
 
I have a feeling that the fact that the TM backup disk is the same size as the startup volume caused this issue. I cannot get a backup going now (see me most recent previous post), and I just found this:
http://discussions.apple.com/thread.jspa?threadID=1625887&tstart=0

Others have had the same issue. If the TM disk gets too close to full, it sometimes stops backing up. Also, the initial backup requires quite a bit more space than the drive being backed up in order to even get it going.

So I'm stuck now. :(

I have two internal 500 GB drives. Can I raid them together and use them as a TM disk for the my 500GB startup disk?
 
A tribute to Mac OS X is the fact that I've never used RAID before and was able, in a few minutes, to set up a striped RAID (0) drive using two internal 500 GB drives, tell Time Machine to use the combined 1 TB drive for the backup volume, and get Time Machine backing up my startup volume. :)

Not to bash any other operating systems, but I'm not sure how easy this would have been if I were not using a Mac. Easy is the name of the game. It saves me time, frustration, and worry. It also saves those around me from the ranting that would occur if RAIDing weren't easier on a Mac.

I still think that requiring twice the size of the volume being backed up is a little overkill on Apple's part, but I've had this other internal drive sitting around as a Tiger clone since about a year ago when I upgraded to Leopard. I guess I can safely say that I won't be needing it any longer.

So, we'll see how it goes with my new RAID volume.
 
You must log in or register to reply here.
Back
Top