I'm having errors with time machine

I checked other discussions and downlaoded a time machine log. The message that comes up is, "Starting standard backup Backing up to: /Volumes/Time Machine Backups/Backups.backupdb Error: (22) setxattr for key:com". Any help?

Usually that error indicates a drive malfunction; specifically, the drive is spinning down and not responding to bus signals. Some "Eco" or "green" drives are known for this behavior. The following steps may help:
Select  ▹ System Preferences ▹ Energy Saver ▹ Power Adapter and uncheck the box labeled Put the hard disk(s) to sleep when possible, if it's checked.
If the drive is connected to a hub, connect it to a built-in port on the computer.
If a firmware update is available for the drive, apply it.
Contact the drive manufacturer to see whether there's a firmware setting you can change.
If you installed vendor software for the drive, uninstall it.
If none of the above steps resolves the issue, try another drive.

Similar Messages

  • Time machine only copies User Info and Users (Applications, Library, and System are missing) from my quad core Mac Pro.  45 Gb of 162 Gb are missing.  Any one having success with time machine copying all folders using Mavericks?   What do I need to do dif

    Time machine only copies User Info and Users (Applications, Library, and System are missing) from my quad core Mac Pro.  45 Gb of 162 Gb are missing.  Any one having success with time machine copying all folders using Mavericks?
    What do I need to do differently?

    The late, great Pondini was investigating that issue before he passed away.
    See here: https://discussions.apple.com/thread/5125969
    I think there might be information there on how to reset Time Machine to do a full backup. I think you basically have to reset it and start over.

  • I am having problems with Time Machine and having enough space to finish my last back up.

    I am having problems with Time Machine and having enough space to finish my last back up.

    Take a look at this link, http://support.apple.com/kb/HT1427

  • -6584 error with time machine

    I just re-installed OSX Lion from scratch.  As instructed by a person from the Genius bar, I made sure to back everything up with time machine before doing this.  I didn't automatically rebuild from time machine as I was having problems with the computer that I didn't want to import.  There are things in time machine that I need, however, and I do want to import them from time machine.
    When I try to "enter" time machine I get a -6584 error.  I have searched Mac support for this error code and get no results.  The sparse bundle is intact, as I can open it from another machine.  When I try to open it from the machine I have installed Lion on, I get the message "Resource temporarily unavailable."
    The Time Capsule I am accessing is a brand new Time Capsule.
    Can someone help me solve this problem???
    Thanks,
    --Kenoli

    stevenfromsa wrote:
    Im having exactly the same issues.
    Really?  You're getting a -6584 error?
    If so, try Repairing your backups, per #A5 in Time Machine - Troubleshooting
    Ive also had problems with the Time Machine filling up unreasonably quickly. It seems to be backing up the same files over and over again!
    See #D4 in the same article. 

  • Errors with Time Machine (not completing backup, and needing to erase the ".inProgress" package)

    I have in a previous discussion been talking about errors with my Time Machine backup.  The errors were with a problem with Indexing a file, it fails and stops the whole backup.  Each time it attemps another backup, it fills my ".inProgress" package with a (nearly) whole backup, filling my Time Machine hard drive, and thus errasing my previous good backups.  The error occurs after about 95% completion.
    In my last post of a similar disscussion, the problem was indexing the Preference Pane files and this caused the whole backup to fail.  This was my last post there:  (below in some additional info of my situation)
    I did exclude the MobileMe.prefPane.  And I got:
    12/16/11 9:24:50.468 PM com.apple.backupd: Starting standard backup
    12/16/11 9:24:50.556 PM com.apple.backupd: Backing up to: /Volumes/3 TB GoFlex Drive/Backups.backupdb
    12/16/11 9:25:14.418 PM com.apple.backupd: Waiting for index to be ready (101)
    12/16/11 9:27:02.366 PM com.apple.backupd: Deep event scan at path:/ reason:must scan subdirs|
    12/16/11 9:27:02.366 PM com.apple.backupd: Finished scan
    12/16/11 9:33:37.119 PM com.apple.backupd: Deep event scan at path:/Volumes/Mac OS Lion GM reason:must scan subdirs|
    12/16/11 9:33:37.119 PM com.apple.backupd: Finished scan
    12/16/11 9:36:15.650 PM com.apple.backupd: 758.92 GB required (including padding), 830.32 GB available
    12/16/11 10:25:14.873 PM com.apple.backupd: Copied 22.8 GB of 630.5 GB, 782749 of 2357620 items
    12/16/11 11:25:15.335 PM com.apple.backupd: Copied 86.6 GB of 630.5 GB, 1167675 of 2357620 items
    12/17/11 12:25:16.227 AM com.apple.backupd: Copied 152.2 GB of 630.5 GB, 1393795 of 2357620 items
    Dec 17 01:25:16 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 305.2 GB of 630.5 GB, 1413946 of 2357620 items
    Dec 17 02:25:16 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 457.1 GB of 630.5 GB, 1419190 of 2357620 items
    Dec 17 03:19:07 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 1736865 files (568.3 GB) from volume Macintosh HD.
    Dec 17 03:25:16 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 572.1 GB of 630.5 GB, 1848939 of 2357620 items
    Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Indexing a file failed. Returned 200 for: /Volumes/Mac OS Lion GM/System/Library/PreferencePanes/Mouse.prefPane, /Volumes/3 TB GoFlex Drive/Backups.backupdb/Tom iMac/2011-12-14-171406.inProgress/7DB524DD-EFB9-42A6-8A21-0A2A312EDA6D/Mac OS Lion GM/System/Library/PreferencePanes/Mouse.prefPane
    Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Aborting backup because indexing a file failed.
    Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Stopping backup.
    Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 2164998 files (581.1 GB) from volume Mac OS Lion GM.
    Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copy stage failed with error:11
    Dec 17 03:40:50 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Backup failed with error: 11
    This time it was the Mouse.prefPane that caused the error.  I'd like to exclude the entire PreferencePanes directory.
    This was my error message this time:
    I just realized this was on my small Developers partition.  Perhaps there is an error with the build, OR an error with the initial restore.  I'd like to perhaps exclude the entire /Volumes/Mac OS Lion GM.  I expect that Time Machine is working fine with my main partition and the error happens when it's almost done with the Mac OS Lion GM partition.
    The problem now is that I only have 265 GB of 3 TB available on my Time Machine HDD.  If attempt another backup, it'll surely erase about 410 GB of my past saved backups.  I've already lost 6 months, and I only have two months left of backups.  I need to erase the ".inProgress" package again.  That'll take time, and it's impossible to do from this main partition, even at root access.  This ".inProgress" has a total of two (nearly) full backups; it didn't cleanup the first full backup attempt while starting the second,perhaps it would have had it finished.  But I fear even if I exclude the whole "Mac OS Lion GM" partition,  It'll create a third full backup before cleanup and erase ~400 GB of previous good backups.  Then, I'll have a total of 4 (nearly) full backups!  3 TB is just enough without any past backups.
    Maybe I'll just copy my documentations of my 'errasing the ".inProgress" package'  last time (from the Mac OS Lion GM partition) and do a full restore of just that partition.  Thus erasing the errors all together.  If it doesn't fix the errors then this could be a bug in the build that doesn't allow Time Machine to work.  I've always included this partition in Time Machine before, even with other Lion builds, so I suspect that it was an error in the initial restore.  (I may be answering my own questions, and that the inital restore (of the small partition) is the problem, and I just need to re-restore the small partition)
    Again, I'm going to have to erase the ".inProgress" file to regain 1.53 TB of space before proceeding.
    Also, I gave myself permission to read the ".Backup.345781513.887697.log", the log that was created last night when I first started Time Machine this last time.  It was interesting, but didn't show the error I could see from the console.
    Right now, mds and mdworker appear to be going crazy even after I just now turned off Time Machine.  I think I'll let it go for the rest of the night.  Then I'll work on erasing the ".inProgress" package from the other partition boot up.
    That was my entire last post.  To add some information, I have two OS X partitons, both Mac OS X Lion.  One is my large main partition, the other is one I don't mind testing with.  I recently replaced my internal hard drive in my iMac and restored from Time Machine both partitions.  This appeared to go smoothly.  But I have yet to create a single successful Time Machine backup since.  At first it was doing a Full Backup, which I didn't like, but now it just aborts around 95% completion.  Each, time, it tries it fills the Time Machine hard drive with duplicate (nearly) full backups errasing my older good backups.  I would like to erase the ".inProgress" file to save space.
    My main question in this new discussion is does anyone know of a good way of erasing the ".inProgress" file? This is so I can preseerve my previous backups.  ACLs and other permissions seem to make it impossible to erase from this startup partition, the one I'm running Time Machine from.  Even at root level, if I give myself permission to change permissions or delete a file, it'll say Operation not Permitted instead of Permission Denied.  I have been able to delete this ".inProgress" package before when booting from the other  partition, but with great difficulty.  I have had much help from another Member in this Support Community when it comes to solving my Time Machine problems.  I think I have found the problem (indexing files in my small OS X partition), as stated in my copy& pasted post above, but I really need to delete this inProgress package first to save space before continuing!

    Pondini wrote:
    Gator TPK wrote:
    Now I'll have to fix the small partition?  How's the best way to do this?  There could be thousands of files that won't index fine.
    See if there's anything you haven't done, that applies, in the pink box of #C3 in Time Machine - Troubleshooting
    Otherwise, since most (or all?) of the indexing errors are in OSX, you might want to just reinstall it.  Something may have gone wrong sometime, that damaged those files.
    I reviewed #C3 in Time Machine - Troubleshooting and I have already done most of those things.  I have just learned something new though:
    When I included my Main OS X partition again, I got an indexing error for the first time for that partition.  I might be interesting to note that the _spotlight process was running, and it's running again (the magnifying glass has a dot and it generically says "Indexing Tom's iMac").  mdworker, mds and backupd processes really are working hard, one moment they used over 500% of my CPU.  It's nice to know for once quad core is good for something other than video encoding.  (Now if they could just get the Finder to do more than 100.1%, only 1 thread is doing 100%, I'd like to see file size calculations 8 times quicker!)
    I never got an indexing error once in the past 2 weeks for that large Mac OS X v10.7.2 main volume, and it had appeared to finish that partition backup before running into problems with my smaller test partition.  Also, I had just updated the smaller test partition with a later build of Mac OS X.  But It appears that the beta builds are clearly not the problem.  I thought I could just restore again (from the December 4th backup) the small partition and both would be fine.
    I'll finish reviewing all the suggestions on Time Machine - Troubleshooting and go from there.  Hopefully, the _spotlight indexing simutaniously was the only problem.  It's strange that the indexing hasn't happened since the original restore last week untill I finally got a good clean complete partial Time Machine backup.  Why would the first Time Machine backup trigger indexing again?
    For now, I'm going to exclude the Main Partition again, and let another good backup run.  And try your suggestions.  (And wait till mds, mdworker, etc. to finish!)
    I have the logs of the first two sucsessful backups and the last two failed backups from the last 3 hours, if that would help.?

  • Having Problems with Time Machine

    After a meltdown of the ext HD that I had been using to backup files, I made the decision to update to 10.5 & start using Time Machine. Bought a new 2TB ext drive (FW 800), updated to 10.5.6 & started running the backup. It ran a full bkup, & seemed fine doing the incremental additions for a week or 2 & then some odd things started happening.
    First iTunes would hang up, then the little Epson scanner software would suddenly launch, & a few other oddities like that occurred. Programs might stop responding & I'd have to force quit (Preview was often affected this way) I noticed whenever these kind of things happened, Time Machine was running.
    I occasionally started having trouble shutting down. It would go all the way down to the background image on the desktop and just stay there. After 5 min I'd hit the power button.
    I left the computer on the last 2 nites thinking that undisturbed, Time Machine could run an updated bkup but each AM I get the flag that it didnt run due to an error.
    After reading some posts here, I verified the ext HD w/ Disc Utility & got this response:
    Invalid key length
    Volume check failed.
    Error: Filesystem verify or repair failed.
    Any suggestions?
    thanks Duane

    Duane Sherwood wrote:
    Thanks for the advice. I'm now getting a flag, when I start up, that says 'the ext HD is not repairable by this computer, its now read only & the drive should be backed up & reformatted'.
    Do you still recommend trying to fix from the OS disc or should I just wipe it clean & start over w/ Time Machine?
    you should just reformat it and start over.
    Is this a poss hard drive defect?
    that's also possible. but try reformatting it as i said. if it doesn't work the drive is defective and should be replaced.
    Thanks, Duane

  • Anyone having trouble with Time Machine?

    Mine will NOT finish any backup so it's constantly running the HD. THe onscreen panel will say
    "Backing up 132,386 items" and "492.2 MB of 492.2 MB" and it just keeps thrashing the drive.
    For hours, I mean.
    I told it to "Stop Backing Up" (on right click popup menu) and then I went into "Time Machine Preferences" and turned it off with the switch and clicked the padlock to lock it in the OFF position, and it's STILL RUNNING.
    The only way I can stop it is reboot, cold.

    Restart your machine if need be and turn it off. If you don't have any data on the TM disk other than TM, then reformat it (with case sensitivity OFF). If you have data on there, then just trash teh TM backup folder. DOnt' forget to empty trash. Turn TM back on and let it do it's thing. Don't browse the drive to see what it's doing; don't start modifying file sto test it out - just leave it be till it's done.

  • Having trouble with Time Machine

    I recently had to reinstall my system software. Now I am trying to restore things like my iPhoto Library, Address Book, Safari Bookmarks and settings etc
    But my Time Machine Back up won't seem to let me go any further back than yesterday ! What have I done wrong and how can I get to my old back ups ?
    HELP !
    Tom

    Restart your machine if need be and turn it off. If you don't have any data on the TM disk other than TM, then reformat it (with case sensitivity OFF). If you have data on there, then just trash teh TM backup folder. DOnt' forget to empty trash. Turn TM back on and let it do it's thing. Don't browse the drive to see what it's doing; don't start modifying file sto test it out - just leave it be till it's done.

  • I am having problem with time machine.

    Before I updated to Maverick my time machine worked fine with no problems. Now two or three times a day it keep disconnecting it's self. I have also noiced the time machine symbol at the top of the screen no longer turns like it used to before I updated.
    I pull the time machine cable out and put it back in again and the time machine kick in and do a back up and do back up's as normal  until it disconnect it's self.
    Any ideas why this is hapening

    It is the old network bug.. since Lion that bug has been there.. it is simply lost the hard disk.
    As I put in this post.. use a manual AFP mount of the hard disk.. But it might not help.
    https://discussions.apple.com/thread/5595460?tstart=0
    I have also noiced the time machine symbol at the top of the screen no longer turns like it used to before I updated.
    Correct.. Apple has fixed it.. !! And welcome to Mavericks.

  • I am having issues with Time Machine. Error message "The backup disk image could not be created.

    Error message "The backup disk image could not be created." I have tried everything I have found online in the community from TM full reset  to changing my computers name. Anything else I can try? I am using a Seagate external HD with a connection through my router. I spent an hour on the phone with seagate and everything is ok on the HD end.
    TM sees it and it is mounted but cannot go any further. HELP?!!!!
    Thanks
    -A

    How should it be connected? It has a usb port and ethernet. The USB on the ExHD looks like the port on the back of my computer, so I would need one wth the same ends? Do they make those?
    I can usually fix most my comp problems myself, but this new ExHD has stumped me.
    Thanks for your help.
    -A

  • I'm having issues with Time Machine since my upgrade to Mavericks, running at a snails pace.  Is anyone else experiencing the same?  WiFi is running fine, disabled all the Anti-Virus, still barely runs.

    Is anyone else experiencing the same?  WiFi is running fine, disabled all the Anti-Virus, still barely runs.
    2013 27" iMac

    I'm having the same issue, mine says prepairing to backup. I let it run for 12 hours and it never performed a backup. I have a Mac Book Pro

  • Macbook won't recognize external Hard Drive and issues with Time Machine

    Hello everyone,
    I have just bought a new Macbook Pro with Mountain Lion and I am currently having problems with Time Machine.
    The issue begun in Snow Leopard: Time Machine was taking too long to backup, and would often not finish the backup because the external hard drive would be unwillingly ejected.
    Now with Mountain Lion I have reformated the drive (Mac OS Journaled) and about a third of the way through had the same issue: the drive was ejected before the backup could be finished. I restarted the machine and it happened again. However, now the computer won't even recognize the external drive when I plug it in. I have also tried to power off/on the drive itself to no progress.
    I have tested the USB port with another drive and the port is fine. I have also tested the usb cable and it is fine. And Disk Utility does not recognize the drive (even when I try the >diskutil list command in terminal).
    Now, I can hear the drive humming normally when I turn it on, and it is not usb-powered (my electricity current does fluctuate).
    Could the interrupted backup procedures have damaged the drive? And if so, wouldn't the computer recognize it anyway?
    It is a 4 year old WD 1 TB that is used exclusively for TM and has never left the house.
    Thank you for your time reading this and let me know if you need any more information that could help out.
    Cheers!

    From your description, I'd suspect a failing drive. Maybe time for a new external, especially as you've already re-formatted and it's still playing up.
    I had a similar problem with one of my clone backups a few weeks ago - it failed, I erased it, re-cloned, worked a couple of times and then it failed again. Disk Utility didn't throw up any errors after re-formatting. I guess all disks die at some point.

  • Can't back up with Time Machine.

    Hi, Im having troble with time machine. When I tried to back up today this error occured.
    The problem may be temporary. Try again later to back up. If the problem persists, use Disk Utility to repair your backup disk.
    Repaired back up with both Disk Utility & Drive Genius. Disk seems to be working fine. But, it won't back up.
    Any help will be appreciated.

    This is more a network problem than a disk error..
    Reboot.. the network.. restart in correct order.. modem router /TC.. clients with 2min gap.
    If you have trouble reset TM and redo it.
    See A4.. http://pondini.org/TM/Troubleshooting.html

  • Trouble with time machine

    I am having trouble with Time Machine. I keep getting several messages:  1.  Mac OS X can't repair the disk "Mona's I MAC"   2.  You haven't selected a location for Time Machine Backups.    
    When I try to select a location there is nothing there to select and the time machine will not stay on.  I have an external back up "my passport" by WD.  Could this be full? 
    Need help.

    I was running backup instead of time machine until I saw snow leopard had time machine improvements. I'm very happy with the performance so far w/ snow leopard (OS X 10.6) time machine performance.

  • Missing backups/lack of space with Time Machine

    Hello,
    I am having trouble with Time Machine since I updated to Mavericks.  Time Machine tells me that I have insufficient space on my external hardrive (1TB) even though in Time Machine it only has one full backup.  If I Get Info on the drive it says Capacity 999.72GB, Available 71.37GB and Used 928,35GB. 
    In Finder I used to be able to delete older backups if needed but generally Time Machine did what it was supposed to - it overwrote old backups.  I can no longer find the files to delete and TM only says I have one full backup.
    How can I uncover these, what appear to be, hidden files? Something must be there as I have no space left!
    The external hard drive is 2TBp partioned, I also seem to have lost all of the data from the non-TM partition, which is not great either.
    Please let me know if you need any other information.
    Thanks in advance for any help.

    Do you use virtualization software, such as VMware, Parallels, or VirtualBox?
    The virtualization software creates a large virtual-disk container that is constantly changing, so it has to be backed up every time Time Machine runs. That will quickly fill up any backup destination.
    You should exclude the virtual-disk file(s) from your Time Machine backups. To do that, click the Options button in the Time Machine preference pane. Back up the files on the virtual disk from within the guest system, using a native backup application.
    A compromise solution is to create a "snapshot" of the virtual machine in the virtualization software (not a Time Machine snapshot.) That will give you a single large file that never changes and only has to be backed up once. All the subsequent changes will be stored in a new file that's initially much smaller, but will grow over time. You should still exclude that file from TM backup. If you ever need to restore the VM from Time Machine, you'll have a working setup, which will make it easy for you to restore the rest of the data from within the guest system.
    Another common cause of large TM snapshots is native OS X disk images. If you store a lot of data on one or more writable disk images, they should be in "sparsebundle" format, which will be backed up much more efficiently than any other format. Also be aware that disk image files are not backed up at all while the image is mounted. Make sure you unmount the image often so it can be backed up. If you ever restore, you will, of course, lose all changes made since the last backup. Consider eliminating large read/write disk images from your workflow, if possible.

Maybe you are looking for