Previous 1 2 3 Next 30 Replies Latest reply: Mar 7, 2014 2:53 PM by callehedberg
Glenn Boley Level 1 Level 1 (0 points)

I have been geting TM errors like this:

 

Starting standard backup

Backing up to: /Volumes/TimeMachine HD/Backups.backupdb

No pre-backup thinning needed: 486.78 GB requested (including padding), 3.48 TB available

Error: (-8088) SrcErr:NO Copying /Library/Frameworks/TSLicense.framework/Versions/A to /Volumes/TimeMachine HD/Backups.backupdb/NewG5/2011-12-24-024737.inProgress/CD3715CD-EBA1-46E6-A17B- FF4D7971A012/Zebra HD/Library/Frameworks/TSLicense.framework/Versions

Error: (-8088) SrcErr:NO Copying /Library/Frameworks/TSLicense.framework/Versions/A/Resources to /Volumes/TimeMachine HD/Backups.backupdb/NewG5/2011-12-24-024737.inProgress/CD3715CD-EBA1-46E6-A17B- FF4D7971A012/Zebra HD/Library/Frameworks/TSLicense.framework/Versions

Error: (-48) SrcErr:NO Copying /Library/Frameworks/TSLicense.framework/Versions/A/SetPrefTool to /Volumes/TimeMachine HD/Backups.backupdb/NewG5/2011-12-24-024737.inProgress/CD3715CD-EBA1-46E6-A17B- FF4D7971A012/Zebra HD/Library/Frameworks/TSLicense.framework

Error: (-48) SrcErr:NO Copying /Library/Frameworks/TSLicense.framework/Versions/A/TSLicense to /Volumes/TimeMachine HD/Backups.backupdb/NewG5/2011-12-24-024737.inProgress/CD3715CD-EBA1-46E6-A17B- FF4D7971A012/Zebra HD/Library/Frameworks/TSLicense.framework

Copied 10373 files (4.4 GB) from volume Zebra HD.

Copied 10382 files (4.4 GB) from volume MyDrive.

 

I have tried everything I know (and I've been using Macs since 1984 - so I'm no novice to this) without success. But then it occurred to me...

 

The drives I'm trying to back-up have moved machines - from an Dual 1.25 GHz G4 MDD to a Dual 2.3 GHz PCIe G5. They function perfectly, boot perfectly and run perfectly - except that I get TM errors which I didn't have under the G4. I have a strange suspicion that this is what's causing the TM failures - some hidden files that "don't match." Short of reinstalling everything from scratch - a pain in the posterior beyond belief - Does anyone have any great ideas? BTW, I have a complete clone of each of the two drives (and booting from either of the clones yields the same TM erors). I was thinking of re-installing the OS from scratch on one of the clones and using the migration utility to install everything I have from one of the other drives. Anyone have any experience with this? I'd hate to waste all that time for nothing...

 

Thanks!


G5, MacBook, iMacs, G4 and many others..., Mac OS X (10.5), 10.6.x on all Intel Machines
  • BDAqua Level 10 Level 10 (120,055 points)

    Hi Glenn,

     

    It looks like bad files on the source Hard Drive.

    The -8088 error is particularly bothersome because Time Machine would trip on this error and then quit but declare success. Any file that would have been backed up after this error occurs will simply not be in the backups set. Fortunately, the Console error message provides the ENTIRE path to the offending file and it can be easily located and deleted or excluded. However, since Time Machine trips on the FIRST bad file that it finds, it has to be run again and again to grind through all of them until it completes without errors. Note, than in 10.5.2, Time Machine may declare a -8088 error, but at least it doesn't choke on it.

    http://www.girr.org/mac_stuff/backups.html

  • Pondini Level 8 Level 8 (38,720 points)

    Glenn Boley wrote:

    . . .

    Error: (-8088) SrcErr:NO Copying /Library/Frameworks/TSLicense.framework/Versions/A to /Volumes/TimeMachine HD/Backups.backupdb/NewG5/2011-12-24-024737.inProgress/CD3715CD-EBA1-46E6-A17B- FF4D7971A012/Zebra HD/Library/Frameworks/TSLicense.framework/Versions

    All the messages are for the TSlicense framework, which apparently is an old Windows Server system.

     

    Try just excluding the entire TSLicense folder  from backups, per #10 in Time Machine - Frequently Asked Questions.

  • Glenn Boley Level 1 Level 1 (0 points)

    Thank you for pointing out the obvious! (No smart-*** answer intended - I completely missed it!) After researching the TSLicense, I found it to be part of Flip4Mac WMV player/plug-in, so I simply trashed the package, erased my Time Machine disk, restarted, and voilá! It works! I'm so glad I didn't re-install everything from scratch. At first I got this log message:

     

    Time Machine errors from previous System log:

     

    Dec 26 15:22:12 NewG5 mds[173]: (Error) Import: importer:0x8ee400 Importer start failed for 501 (kr:268435459 (ipc/send) invalid destination port)

     

    Dec 26 15:22:16 NewG5 mds[173]: (Error) Import: importer:0x8ee400 Importer start failed for 501 (kr:268435459 (ipc/send) invalid destination port)

     

    Dec 26 21:29:10 NewG5 mds[172]: (Error) Import: importer:0x8a0200 Importer start failed for 89 (kr:268435459 (ipc/send) invalid destination port)

     

    Dec 26 21:29:14 NewG5 mds[172]: (Error) Import: importer:0x8a0200 Importer start failed for 89 (kr:268435459 (ipc/send) invalid destination port)

     

     

     

         ************ NOTE ************

    Your Time Machine Backup drive may be conflicting with Spotlight Search indexing.

     

    Click on the Help Button and find “Importer Start failed”, for help on this topic.

     

    Then. it completed and I got this:

     

    No Time Machine Errors to report in the current log.

    Try the previous log

     

    Last Successful Backup Message:

    Dec 27 09:38:18 NewG5 /System/Library/CoreServices/backupd[13296]: Backup completed successfully.

     

    Thanks, and YeeHa!!

  • Pondini Level 8 Level 8 (38,720 points)

    Glenn Boley wrote:

    . . .

    Time Machine errors from previous System log:

     

    Dec 26 15:22:12 NewG5 mds[173]: (Error) Import: importer:0x8ee400 Importer start failed for 501 (kr:268435459 (ipc/send) invalid destination port)

     

    . . .

    Your Time Machine Backup drive may be conflicting with Spotlight Search indexing.

     

    Click on the Help Button and find “Importer Start failed”, for help on this topic.

    . . .

    No Time Machine Errors to report in the current log.

    Try the previous log

     

    Last Successful Backup Message:

    Dec 27 09:38:18 NewG5 /System/Library/CoreServices/backupd[13296]: Backup completed successfully.

    Most of those aren't really Time Machine messages.  Are you using a 3rd-party utility that claims to show what's going on with Time Machine?  If so, at least one of them does not do a very good job, and in some cases acually generates some messages of it's own!  Some of them are inaccurate or spurious.

     

    I'd strongly recommend the Time Machine Buddy widget, per #A1 in Time Machine - Troubleshooting.  It just extracts the actual messages from your logs.

     

    Thanks, and YeeHa!!

    Great!  Glad it's sorted out.

  • BDAqua Level 10 Level 10 (120,055 points)

    Good news Glenn, thanks!

  • Glenn Boley Level 1 Level 1 (0 points)

    Time Machine Buddy is EXACTLY where I got the generated info. It IS amazing how one, seemingly completely unrelated file (TSLicense) can bring TM to its knees. Gland that's sorted out already. Thanks for your reply.

  • BDAqua Level 10 Level 10 (120,055 points)

    For my money TM is the worst backup solution outside of no backup at all!

  • Pondini Level 8 Level 8 (38,720 points)

    How wonderfully helpful.

     

    How can we ever thank you enough for that constructive assistance?

  • Pondini Level 8 Level 8 (38,720 points)

    Glenn Boley wrote:

     

    Time Machine Buddy is EXACTLY where I got the generated info.

    The ones in your first post, yes.

     

    But not the ones quoted in my previous post.  There's nothing wrong with them, exactly, but some weren't sent by Time Machine and may be misleading.

  • Pondini Level 8 Level 8 (38,720 points)

    Glenn Boley wrote:

    . . .

    It IS amazing how one, seemingly completely unrelated file (TSLicense) can bring TM to its knees

    That may seem to be a disadvantage, but usually the damaged item(s) it finds are recently-acquired music, photo, or video files, or a spreadsheet you thought you were done with for a few weeks or months.

     

    Would you rather Time Machine find those problems on the next backup, when you may still have a chance to fix them, or (like most other backup apps) just blindly copy the good, the bad, and the ugly, so you don't know there's a problem until you try to use the file?

  • Glenn Boley Level 1 Level 1 (0 points)

    Happy New Year. I appologize for not responding sooner. Two things:

     

    1. ALL the data I posted was from TM-Buddy - both sets of data. Don't know where it got it from (I would assume the System logs), but I copied them straight from TMB.

     

    2. It is DEFINITELY a disadvantage handled the way it is. First of all, there was no real warning (other than from TMB) that WEEKS worth of backups were incomplete! TM didn't tell me they failed. The big clue I got was that it seemed that TM was using waaay too much processor time and resources, which made me download TMB to begin with - otherwise, when I really needed it, it would have failed me. (Luckily, I have daily clones of each drive, too. As one wise man said, "There are two kinds of people in this world. Those who back-up, and those who wish they had.") Failing due to a bad file would be perfectly fine if TM reported a failure, but not when it leads one to believe everything is fine and dandy. A far better approach would be to complete the whole backup and report a file failure.

     

    Don't get me wrong. I'm a big fan of TM, and have used it successfully for a long time without any problem. This one little glitch was a problem, that, luckily, I found before it was too late.

     

    -G

  • Pondini Level 8 Level 8 (38,720 points)

    Glenn Boley wrote:

     

    Happy New Year. I appologize for not responding sooner. Two things:

     

    1. ALL the data I posted was from TM-Buddy - both sets of data. Don't know where it got it from (I would assume the System logs), but I copied them straight from TMB.

    Sorry, but no, they're not: 

    Dec 26 15:22:12 NewG5 mds[173]: (Error) Import: importer:0x8ee400 Importer start failed for 501 (kr:268435459 (ipc/send) invalid destination port)

     

    That message was sent by mds, not Time Machine, and will not appear in Time Machine Buddy.  Among other things, TM Buddy does not show the date, time, and computer name (in the first part of the message)

     

    I've never seen these:

    Your Time Machine Backup drive may be conflicting with Spotlight Search indexing.

    Click on the Help Button and find “Importer Start failed”, for help on this topic.

    or this one:

    No Time Machine Errors to report in the current log.

    Try the previous log

    That sounds like a different utility (the name of which I've forgotten, but is SIMILAR to Time Machine Buddy).

     

    The Time Machine Buddy display is like this:

     

    shapeimage_2.png

     

    2. It is DEFINITELY a disadvantage handled the way it is. First of all, there was no real warning (other than from TMB) that WEEKS worth of backups were incomplete! TM didn't tell me they failed.

    In almost all cases, Time Machine fails when it can't copy a file.  It sends either "An error occurred while copying files to the backup volume" or "Aborting backup because indexing a file failed."  On occasion, it just says "Backup failed" without any further explanation.  But in those cases, there are messages in the system.log (which TM Buddy will display), naming the file in question.

     

    Perhaps somehow it knew it could just skip those particular files and continue, but it's very rare.

  • Glenn Boley Level 1 Level 1 (0 points)

    Ooops! Mea culpa. It was from TM Error Logger, not TMBuddy. And you are correct about "most of the time" - except THIS time - where it usually tell you it failed. This time, the backup was aborted - but it reported a successful backup anyway. For such a big fan of TM, you seem to know an awful lot about how and why it fails (for which I'm grateful), but this leads me to the conclusion that you have seen it fail an awful lot.

  • Pondini Level 8 Level 8 (38,720 points)

    Glenn Boley wrote:

     

    Ooops! Mea culpa. It was from TM Error Logger, not TMBuddy.

    Ah, yes, now I remember the name.  Haven't heard about it in quite a while.  The problem with it is, it tries to "interpret" the actual messages and convert thm into something easier to understand, but in many cases makes it harder.

     

    this leads me to the conclusion that you have seen it fail an awful lot.

    I've used it for several years, including lots of testing, and have had it fail only once for me  (other than hardware problems or during beta testing). 

     

    But with several million folks using it, yes, as with any app, a few will have problems.  Most are things people don't understand, or have done things they shouldn't (at least partly because there isn't good, easily found documentation);  or hardware problems or damaged/corrupted files (also often hard for the casual user to figure out because of the inadequate messages and documentation).

     

    No app is perfect (even the ones I wrote ).

Previous 1 2 3 Next