Time Machine fails intermittently to start backup

I am running MBPro Retina laptop with Mountain Lion 10.8.4, with all current updates (except for the new v. 6.3 for Airport Utility, which does not work right on my machine and many others). I am using a relatively new 2GB Time Capsule for backup via a wireless connection. The connection appears to be stable (as indicated by the console log) and I do not think that issue is relevant here. I backup has been working very well for many months but started to act up several weeks ago with a intermittent error (see below).
I get a successful backup about 1 out 3 times, so the situation is annoying but not fully critical. I include below a listing from the console showing the relevant part of the log for a failed initation of the backup (personal information is redacted with XXXX). I have searched out error messges for the DiskMountedNotifier and have little to help isolate the problem. Can someone help point me in the right direction??
6/21/13 10:45:15.686 AM com.apple.backupd[7009]: Starting automatic backup
6/21/13 10:45:16.000 AM kernel[0]: nspace-handler-set-snapshot-time: 1371825917
6/21/13 10:45:16.844 AM com.apple.backupd[7009]: Attempting to mount network destination URL: afp://XXXX;[email protected]/Data
6/21/13 10:45:25.400 AM com.apple.backupd[7009]: Mounted network destination at mount point: /Volumes/Data using URL: afp://XXXX;[email protected]/Data
6/21/13 10:45:25.000 AM kernel[0]: AFP_VFS afpfs_mount: /Volumes/Data, pid 7012
6/21/13 10:45:25.000 AM kernel[0]: AFP_VFS afpfs_mount : succeeded on volume 0xffffff81d0440008 /Volumes/Data (error = 0, retval = 0)
6/21/13 10:45:41.127 AM DiskMountedNotifier[279]: Try #0, for SXvN, result = -600
6/21/13 10:45:43.129 AM DiskMountedNotifier[279]: Try #1, for SXvN, result = 0
6/21/13 10:45:43.129 AM DiskMountedNotifier[279]: launch for id = 0 NvXS event = Mscn result = 0
6/21/13 10:46:28.636 AM com.apple.backupd[7009]: Failed to eject volume /Volumes/Data (FSVolumeRefNum: -122; status: -47; dissenting pid: 0)
6/21/13 10:46:28.636 AM com.apple.backupd[7009]: Waiting 60 seconds and trying again.
6/21/13 10:47:28.712 AM com.apple.backupd[7009]: Network destination already mounted at: /Volumes/Data
6/21/13 10:48:25.199 AM com.apple.backupd[7009]: Failed to eject volume /Volumes/Data (FSVolumeRefNum: -122; status: -47; dissenting pid: 0)
6/21/13 10:48:25.199 AM com.apple.backupd[7009]: Waiting 60 seconds and trying again.
6/21/13 10:49:25.967 AM com.apple.backupd[7009]: Network destination already mounted at: /Volumes/Data
6/21/13 10:50:07.809 AM coreaudiod[160]: Disabled automatic stack shots because audio IO is active
6/21/13 10:50:10.047 AM coreaudiod[160]: Enabled automatic stack shots because audio IO is inactive
6/21/13 10:50:22.889 AM com.apple.backupd[7009]: Failed to eject volume /Volumes/Data (FSVolumeRefNum: -122; status: -47; dissenting pid: 0)
6/21/13 10:50:22.890 AM com.apple.backupd[7009]: Giving up after 3 retries.
6/21/13 10:50:32.928 AM com.apple.backupd[7009]: Backup failed with error: 21
6/21/13 10:50:32.988 AM com.apple.backupd[7009]: [SnapshotUtilities mountPointForVolumeRef] FSGetVolumeInfo returned: -35
6/21/13 10:50:32.988 AM com.apple.backupd[7009]: Failed to eject volume (null) (FSVolumeRefNum: 0; status: -35; dissenting pid: -1)
6/21/13 10:50:32.988 AM com.apple.backupd[7009]: Failed to eject Time Machine disk image: /Volumes/Data/Queets.sparsebundle
6/21/13 10:50:33.064 AM UserNotificationCenter[7065]: *** WARNING: Method userSpaceScaleFactor in class NSWindow is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead.

I have used the above to fix a Time Machine issue. I had a problem with my backup and after recovering the
sparsebundle I still could not get the backup to run.
The error message I had initially was
sparse bundle could not be accessed (error -1)
I took correctve action from these useful sites and recoved the sparsebundle
http://www.pondini.org/TM/C17.html
http://blog.jthon.com/?p=31
But the message "sparse bundle could not be accessed (error -1)" just would not go away and
In the system log I had this message repeated 3 times for each backup attempt.
26/08/2013 21:43:27.269 com.apple.backupd[434]: Failed to eject volume /Volumes/Data (FSVolumeRefNum: -105; status: -47; dissenting pid: 0)
The final thing I needed to do was remove /Volumes/Time Machine Backups. I think it was dated from when my backup first got corrupted.

Similar Messages

Time Machine fails when trying to backup user folder

When I try to backup my OSX 10.6.7 MB Pro to either an USB-attached external disk or a time capsule the backup fails shortly after the scan run, leaving me with the message "The backup was not performed because an error occured while copying files to the backup disk." The scan run is taking quite some time (more than 300'000 objects),,
Only if I exclude my own user folder (respectively the ~) from backup the timemachine backup runs smoothly, but of course without my user data.
The MB has an SSD with 250 GB capacity of which 188 GB are used.
If you can assist in any way, many thanks to you!
Kind regards
Stefan

Not one of Apple's best messages.
See #C3 in Time Machine - Troubleshooting. It will show you how to locate the message(s) that describe the problem, then help you fix it. If that doesn't help, post back with details, including all the messages, your setup, what you've done, and the results.

Time Machine fails when trying to backup

I have a macbook running 10.5.8. I am trying to use time machine with my iomega external hard drive but I keep getting an error that the backup failed. I have been successful with backups in the past with this same hard drive. Any ideas what's going on

unfortunately there is no fix for this and there never will be
unless you sell both boxes and get a Time Capsule
in the meantime you need to mount the drive you are backing up to
select it as your backup drive in time machine then unmount it (drag to trash can)
and let time machine mount it
of course once it's mounted your next scheduled backup will also fail
so unmount it every time or turn off time machine and do backups every once in while

Time Machine Fails When Trying to Backup Certain Files

Time Machine is having problems with some files I have copied from a Windows computer. I am a web developer and I moved my client files from a Windows PC to my iMac. Most of the files backup properly but some don't. When Time Machine tries to backup those files, it fails.
I downloaded Time Machine Buddy and it has helped me identify files that can't be backed up. However, the only solution that works is to delete the files. *Since these are client files, that is not an acceptable solution.*
When I look at "Get Info", there are several listings for admin, system, staff, owner, and everyone. Each list shows the permissions to be "Custom." I have changed some to "Read and Write" and I have changed all of them to "Read and Write." Neither of these have fixed the problem. Time Machine still fails on the same files.
I really need some smart Mac person to tell me what I can do to fix this problem. Thanks.

Csound1 wrote:
Correct, at no time did I say that this was for everyone, it is in fact for anyone who wishes to spend his time working rather than restoring.
For most folks, a hard drive failure is not exactly common. If they are to you, something is seriously wrong.
Replacing a drive in a unibody MBP is a 5 minute operation! & they are cheap!
Yes, for those who are mechanically inclined and not afraid to open up a Mac. What percentage of users do you suppose that is?
As to your second point, I suggested specifically using a TM type backup in addition to the clone, I stated that my choice is a realtime service that stores my files (a) as files that I can access from anywhere (b) with versions (including deletions) going back as far as my storage limits allow.
And how would you use that to roll back to a previous version of your entire system?
I don't want to have to deal with TM permissions/user/network/extreme/forgetting to delete till it gets full blahblahblah
Huh? Now you're adding all sorts of other things.
Permissions? A user account is a user account, and Time Machine maintains the permissions.
Network? Your clone is on a network? How do you boot up from that?
Extreme? You use an Airport Extreme for your network clone?
Forgetting to delete until it's full? Yes, that's exactly what you mentioned above: "versions (including deletions) going back as far as my storage limits allow."
PleasePondini, do it your way and I'll do it mine
Obviously.

Time machine fails on new iMac

I upgraded to a new 21.5" iMac from a g5 iMac. I transferred my files and have two external hard drives one with photos and one for time
(all worked great on the g5). Main programs in use on the g5 is lightroom and iTunes for the iPhone and iPad. I have been unable to get time machine to work with my files installed. Both the iMac and backup drive have been replaced with no results. When ihave a clean system with my files I have been able to use time machine for two days before it failed at best.
Every time time machine fails my system starts to act strange and I am forced to do a wipe and reinstall. Have done a complete wipe and install on the iMac and reformatted the new external drive (have left the photo drive off as I got a failure with out that drive connected). I have not installed any of my files and so far time machine works. I suspect some sort of corrupt file. Any suggestions on the next steps? I plan an waiting a few more days on the backups just to be sure they work without my files or programs installed.

Wire fox terrier wrote:
Is there any software that can detect corrupt files? Disk utilities says all drives are fine.
Not really.
Disk Utility (and other similar apps) check the File System on the disk (the various directories, catalogs, etc., for completeness and consistency, not the internal layout of each file.
Since different kinds of files have different data layouts, and no central registry of the rules, there's no realistic way to check all the possibilities.
Unlike most backup apps, Time Machine does index them, however, and in the process sometimes finds problems. If there's a serious problem, it normally sends a message naming the file, then fails, so you can exclude the file from being backed-up, fix it, or delete it.
Considering the symptoms you're seeing, it's likely either an intermittent hardware problem, or something you dragged from your G5 was already damaged, or damaged in the process, or came from a different OS (like Windoze) and didn't get translated properly. Since you get no messages, it's going to be very tedious to narrow it down.
From your previous post:
Both a capture program from apple tech and send to apple via about this Mac (system profiler) would not work.
Do you mean they wouldn't run properly, or you sent them to Apple and they either haven't responded or said they couldn't find anything?

How can I force Time Machine to make a complete backup of my Hard Drive. I just installed a new external drive for Backup since my previous one failed. Now when I back up, Time Machine only backs up my data folder and the Users folder.

How can I force Time Machine to make a complete backup of my Hard Drive. I just installed a new external drive for Backup since my previous one failed. Now when I back up, Time Machine only backs up my data folder and the Users folder.
When I start a backup. Time Machine says "Oldest Backup: None; Latest Backup: None", so it seems like it should do a complete backup, but it only does a partial.

Hi I'd like to jump in here. Your app showed me this:
Time Machine:
          Skip System Files: NO
          Mobile backups: OFF
          Auto backup: YES
          Volumes being backed up:
                    Macintosh HD: Disk size: 749.3 GB Disk used: 453.81 GB
          Destinations:
                    Plastic Wrapper [Local] (Last used)
                    Total size: 999.86 GB
                    Total number of backups: 64
                    Oldest backup: 2013-07-24 23:25:11 +0000
                    Last backup: 2013-11-17 01:40:47 +0000
                    Size of backup disk: Too small
                              Backup size 999.86 GB < (Disk used 453.81 GB X 3)
          Time Machine details may not be accurate.
          All volumes being backed up may not be listed.
          /sbin excluded from backup!
          /usr excluded from backup!
          /System excluded from backup!
          /bin excluded from backup!
          /private excluded from backup!
          /Library excluded from backup!
          /Applications excluded from backup!
Aside from the size of my backup drive, which I will increase at some point, I'd really like to have time machine backing up all system folders, especially Applications. How to I reset this hidden exclusions?
Thanks,
Darcy

Time Machine spends hours partially backing up and then fails with "Time Machine couldn't complete the backup due to a network problem." Tried suggestions I've seen on the forum.

Time Machine spends hours partially backing up and then fails with "Time Machine couldn't complete the backup due to a network problem." I've tried various suggestions I've seen on the forum but nothing has worked. TIme Machine worked fine for the last two years and just suddenly started having this problem every time. The only thing that was a little different is that the computer was off for a week while on vacation and then I added a large amount (20 GB) of photos. Now the requested backup size is 82GB, which is large, and process proceeds very slowly for 2-3 hours before failing with the message mentioned. I have more than enough available backup storage space for it. Before failing, Time Machine has backed up no more than 12GB or so of the backup. It fails during different files each time.
I've turned off the computer sleep feature, and I've checked that the NAS is set to never automatically power down. I normally backup over Wi-Fi, but I've also tried connecting to Ethernet and it still has the same problem. It's odd because I also have a MacBook Pro that is still backing up fine to the same NAS using the MacBook's Time Machine.
I am using an iMac with OS X 10.6.8 and an Iomega StorCenter ix2-200 NAS.
I have system logs that I can share if helpful. The logged messages vary a bit from run to run, but here are some messages that I've been seeing:
I always get this message near the beginning of the backup:
Event store UUIDs don't match for volume: Macintosh HD
I've gotten this messsage a number of times:
Bulk setting Spotlight attributes failed.
One Day
Stopping backupd to allow ejection of backup destination disk!
Another day
1/7/12 10:44:20 AM
mDNSResponder[18]
PenaltyTimeForServer: PenaltyTime negative -112916, (server penaltyTime -1132397006, timenow -1132284090) resetting the penalty
1/7/12 10:46:37 AM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x1106be94
1/7/12 10:46:37 AM
kernel
AFP_VFS afpfs_DoReconnect started /Volumes/TimeMachine prevTrigger 0 currTrigger 1
Another Day
1/6/12 8:03:22 AM
Google Chrome[164]
Cannot find function pointer CMPluginInFactory for factory 3487BB5A-3E66-11D5-A64E-003065B300BC in CFBundle/CFPlugIn 0x16f99e20 </Users/smarmer/Library/Contextual Menu Items/Google Notifier Quick Add CM Plugin.plugin> (not loaded)
1/6/12 8:04:02 AM
com.apple.backupd[193]
Copied 7.5 GB of 67.0 GB, 8866 of 8866 items
1/6/12 8:06:58 AM
/System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheServer[1013]
No valid tickets, timing out
1/6/12 8:29:44 AM
mDNSResponder[19]
PenaltyTimeForServer: PenaltyTime negative -148702, (server penaltyTime 2056822773, timenow 2056971475) resetting the penalty
1/6/12 8:59:22 AM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xa5ac380
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect started /Volumes/TimeMachine prevTrigger 0 currTrigger 1
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: soft mounted and hidden volume so do not notify KEA for /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
Another day
1/5/12 3:48:55 PM
mdworker[2128]
CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
1/5/12 4:24:54 PM
mDNSResponder[19]
PenaltyTimeForServer: PenaltyTime negative -42698, (server penaltyTime 1148718961, timenow 1148761659) resetting the penalty
1/5/12 4:29:58 PM
com.apple.backupd[2074]
Copied 586.4 MB of 67.0 GB, 9891 of 9891 items
1/5/12 4:39:00 PM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xa1c0380

bokon0n wrote:
1/11/12 8:53:30 AM
com.apple.backupd[1169]
Warning: Destination /Volumes/TimeMachine does not support TM Lock Stealing
1/11/12 8:53:30 AM
com.apple.backupd[1169]
Warning: Destination /Volumes/TimeMachine does not support Server Reply Cache
Those indicate that your NAS is not fully compatible with Snow Leopard.
1/11/12 8:53:35 AM
kernel
jnl: disk2s2: replay_journal: from: 67182592 to: 78680064 (joffset 0xa7b8000)
1/11/12 8:53:39 AM
kernel
jnl: disk2s2: examining extra transactions starting @ 78680064 / 0x4b09000
1/11/12 8:53:39 AM
kernel
jnl: disk2s2: Extra txn replay stopped @ 79056896 / 0x4b65000
1/11/12 8:53:49 AM
kernel
jnl: disk2s2: journal replay done.
1/11/12 8:53:49 AM
fseventsd[41]
event logs in /Volumes/Time Machine/.fseventsd out of sync with volume. destroying old logs. (253512 14 253512)
1/11/12 8:53:50 AM
kernel
hfs: Removed 1 orphaned / unlinked files and 0 directories
That looks like a problem was found with the file system (data) on the TM disk. I don't know the details, but OSX tried to recover it from the journal, and found extra data on the drive. Likely a result of the incompatibility mentioned above.
1/11/12 9:47:40 AM
com.apple.backupd[1169]
Bulk setting Spotlight attributes failed.
That's a problem writing to the NAS drive.
But the backup continued after all this.
1/11/12 1:25:07 PM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x9d00b44
Something caused a disconnect. Can't tell from the log what it was.
I doubt it's a problem with something in OSX being damaged or corrupted, but reinstalling OSX isn't a major hassle, so might be worth a try.
To be incompatible with Snow Leopard, this NAS must be at least a couple of years old. It may be beginning to fail.
Contact the maker. See if there's an update to make it compatible with Snow Leopard. If so, that might fix it.
If not, or if that doesn't fix it, see if they have any diagnostics that will shed any light.

Time machine fails backing up with a "backup disk not found" error after upgrade to Lion 10.7.2

Time machine fails backing up with a "backup disk not found" error after upgrade to Lion 10.7.2. I've erased and reformatted the drive; reconnected Time Machine(it saw it) and began a new backup. The backup starts again but fails before completing with backup drive not found error. I used the 10.7.2 combo update. Any help on how to fix this problem would be appreciated.

Arghhhhhhhhhhhhhhhhhhh!!!!!!
After waiting since October for a fix, I have now upgraded the firmware on the Time Capsule and installed the new Airport Utility, released yesterday, and the situation is even worse.
Up until now, the Airport Utility had an option to disconnect all drives manually and the Time Capsule would then work until the next reboot – a temporary (?) work-around.
Now that option does not exist in the new-look Airport Utility. And the Airport Utility installation can’t be rolled back and the old utility won’t restore.
The sparesbundle is still not accessible. Anyone worked out a work-around in the new environment yet?
I have another Time Machine backup working fine to a trusty old Lacie Drive so erased the one on my Time Capsule to see if that works. I have renamed the Capsule and the Time Capsule Drive. But to build another full backup will take at least two days and I shall be away from tomorrow and am reluctant to leave the Capsule and computer up and running for a week. And I’ll bet the sparsbundle will still be nowhere to be found.
How can Apple screw up so badly when they are to become the richest company in the entire world and – soon – will have more cash in the bank than the entire United States? Can’t they afford someone who really can sort this out? Especially when a Firewire connected hard drive – my trusty and simple LaCie – works fine.
Words, almost, fail me.

Time Machine fails - cannot make backup folder

For the past two weeks I've been having some major issues backing up my computer with Time Machine. It's become quite a process.
iMac 27"
Mountain Lion
I am backing up to a brand new - well bought in February, '14 - 1TB external hard drive and there is NOTHING else in there except the TM backups.
For the past two weeks it's been failing the automatic backups.
There is PLENTY of room on the drive.
The exact error message reads:
"Time Machine Error
Unable to complete backup. An error occurred while creating the backup folder
Latest successful backup: [time and day entered here]"
To remedy this at first it was as easy as un-mounting the drive and then plugging it back in and it was fine.
Now I've got the disk utility open and constantly repairing the drive and this is only a temporary solution.
Below is a small sample of the report from the utility each one is dated.
Can anyone tell me how to fix this without having to purchase a new drive?
In February the old external drive I had started to freak TM out and it just erased ALL my backups which I desperately needed due to the same error / failure. That drive had plenty of space as well but I lost all my stuff anyway.
I searched the forums for a solution and found nothing helpful.
I know the TM isn't for archiving and another question I have is, How can I transfer or even rename the backup folder that TM makes and move it to a 'free drive' to prevent overwriting? Right now I just keep buying new drives which is ridiculous.
JUNE 16, 2014
Verifying volume “Shuttlecraft 2”
Checking file systemJournal need to be replayed but volume is read-only
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Incorrect number of extended attributes
(It should be 1355781 instead of 1355778)
Incorrect number of Access Control Lists
(It should be 1355741 instead of 1355738)
Checking multi-linked directories.
Checking volume bitmap.
Checking volume information.
The volume Shuttlecraft 2 was found corrupt and needs to be repaired.
Error: This disk needs to be repaired. Click Repair Disk.
Verify and Repair volume “Shuttlecraft 2”
Checking file systemChecking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Incorrect number of extended attributes
(It should be 1355768 instead of 1355765)
Incorrect number of Access Control Lists
(It should be 1355728 instead of 1355725)
Checking multi-linked directories.
Checking volume bitmap.
Checking volume information.
Repairing volume.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking multi-linked directories.
Checking volume bitmap.
Checking volume information.
The volume Shuttlecraft 2 was repaired successfully.
Volume repair complete.Updating boot support partitions for the volume as required.
JUNE 17,2014
Verifying volume “Shuttlecraft 2”
Checking file systemChecking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking multi-linked directories.
Checking volume bitmap.
Checking volume information.
The volume Shuttlecraft 2 appears to be OK.
Verifying volume “Shuttlecraft 2”
Checking file systemPerforming live verification.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking multi-linked directories.
Checking volume bitmap.
Checking volume information.
The volume Shuttlecraft 2 appears to be OK.
June 18,2014
Verifying volume “Shuttlecraft 2”
Checking file systemJournal need to be replayed but volume is read-only
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking multi-linked directories.
Checking volume bitmap.
Checking volume information.
The volume Shuttlecraft 2 was found corrupt and needs to be repaired.
Error: This disk needs to be repaired. Click Repair Disk.
Verify and Repair volume “Shuttlecraft 2”
Checking file systemChecking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking multi-linked directories.
Checking volume bitmap.
Checking volume information.
The volume Shuttlecraft 2 appears to be OK.
Volume repair complete.
Updating boot support partitions for the volume as required.
June 19, 2014
Verifying volume “Shuttlecraft 2”
Checking file systemJournal need to be replayed but volume is read-only
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking multi-linked directories.
Checking volume bitmap.
Checking volume information.
The volume Shuttlecraft 2 was found corrupt and needs to be repaired.
Error: This disk needs to be repaired. Click Repair Disk.
Verify and Repair volume “Shuttlecraft 2”
Checking file systemChecking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking multi-linked directories.
Checking volume bitmap.
Checking volume information.
The volume Shuttlecraft 2 appears to be OK.
Volume repair complete.Updating boot support partitions for the volume as required.
June 20, 2014
Verifying volume “Shuttlecraft 2”
Checking file systemJournal need to be replayed but volume is read-only
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Incorrect number of extended attributes
(It should be 1364328 instead of 1364323)
Incorrect number of Access Control Lists
(It should be 1364285 instead of 1364280)
Checking multi-linked directories.
Checking volume bitmap.
Checking volume information.
The volume Shuttlecraft 2 was found corrupt and needs to be repaired.
Error: This disk needs to be repaired. Click Repair Disk.Verify and Repair volume “Shuttlecraft 2”
Checking file systemChecking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Incorrect number of extended attributes
(It should be 1364316 instead of 1364311)
Incorrect number of Access Control Lists
(It should be 1364273 instead of 1364268)
Checking multi-linked directories.
Checking volume bitmap.
Checking volume information.
Repairing volume.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking multi-linked directories.
Checking volume bitmap.
Checking volume information.
The volume Shuttlecraft 2 was repaired successfully.
Volume repair complete.
Updating boot support partitions for the volume as required.

OK well Time Machine backed up a little bit within the last hour since I posted the above. As I'm sitting here working the backup stops and I get this stupid error again:
So as usual, I go to eject it and I get this ridiculous message. I have no idea what could be 'using' this disk! It's not attached to any programs.
It's got one folder of images and pdf files and the time machine backup on it.
So I force eject it and plug it back in. But if I drop down the little circle at the top task bar for the backup info, It says it backed up successfully at 3:20.
GAH! What the *&^% is wrong with this infernal machine?

Time Machine Failed to Backup

Time Machine failing to backup last few days. Tried Disk Utility disk repair. Failed, with response, "Could not unmount disk." Installed Time Machine Buddy and copied this message:
Starting standard backup
Backing up to: /Volumes/Backup HD-1/Backups.backupdb
Error: (22) setxattr for key:com.apple.backupd.ModelID path:/Volumes/Backup HD-1/Backups.backupdb/WuLi’s MacBook Pro size:13
Error: (-50) Creating directory 2011-12-23-204707.inProgress
Failed to make snapshot container.
Error: (22) setxattr for key:com.apple.backupd.ModelID path:/Volumes/Backup HD-1/Backups.backupdb/WuLi’s MacBook Pro size:13
Backup failed with error: 2
Any help appreciated.

Hi, TM is such a pain & the worst Backup App I've ever ebcountered outside of no backup at all, that being said the great Pondini has covered most all of it's problems here...
http://pondini.org/TM/Troubleshooting.html
http://pondini.org/TM/C10.html
Not that it helps much but...
unitEmptyErr = -22, /*I/O System Errors*/
What Brand/Model External drive is this?

My Macbook pro Early 2008 is randomly slow at starting up and when I am backing up to my time capsule I am receiving the following message 'Time machine could not complete the backup. '' ''The backup disk image ''/Volumes/name time capsule/ my name MacBoo

My Macbook pro Early 2008 is randomly slow at starting up and when I am backing up to my time capsule I am receiving the following message 'Time machine could not complete the backup. '' ''The backup disk image ''/Volumes/name time capsule/ my name MacBook Pro (4).sparsebundle'' could not be accessed (error-1).
Problem started after deleting parrell desktop and window7 ?
Please help?

Look at the more like this column on the right.. this is the most frequently asked question in this discussion area.
Reboot the TC.. restart the whole network if the simple reboot did not work.. start in order. modem.. router/TC.. clients. 2min gap.
Read C12 here. http://pondini.org/TM/Troubleshooting.html

TS1550 Back up to time machine failed. Error, "Files can't be copied onto the backup disk because it appears to be read-only". Back up has been working. drive is not read only. How do I fix this?

Back up to time machine failed. Error, "Files can’t be copied onto the backup disk because it appears to be read-only". Back up has been working. drive is not read only. How do I fix this?

Hello,
http://pondini.org/TM/C6.html

TS1550 Time Machine worked fine w. new HD for 16 backups, but started giving this mssg: [TIME MACHINE COULDN'T COMPLETE THE BACKUP TO "TOSHIBA EXT" ...An error occurred while creating the backup folder]

Time Machine worked fine w. new HD for 16 backups, but started giving this mssg: [TIME MACHINE COULDN'T COMPLETE THE BACKUP TO "TOSHIBA EXT" ...An error occurred while creating the backup folder]

Make sure your hard drive is formatted properly for the operating system installed. Go to Apple menu -> About This Mac to determine what it is. You posted to the 10.5 forum, but your signature says you have 10.9. Here is the tip on what formatting supports what operating systems:
https://discussions.apple.com/docs/DOC-3003

Time Machine couldn't complete the backup due to a network problem

Firstly apologies for the long post, I've been bottling these problems up and could now use some expert advice.
I have a MacPro (10.6.3) with four internal drives (320GB system/apps. + 3x 750GB data, images etc) and a MacBook Pro (10.6.6) with a 320GB internal. With so much accumulated data (Mac user since SE FDHD) I wanted a reliable means to backup all my projects, books, papers, research, images etc. I had several bad experiences using Iomega drives (Ultramax and Storcentre) which were not very Mac compatible and shifted over to a 10TB LaCie 5Big Network 2 which is promoted as Time Machine compatible. Set up Time Machine (with a few hiccups) in Sept 2010 and it ran perfectly, backing up both main computers until March 2011. I have now experienced a string of problems backing up the MacPro, some of which have been resolved speaking to people, some by checking forums and some by using my own noddle to figure it out. The latest error message I am getting is "Time Machine couldn't complete the backup due to a network problem. Make sure your computer and the backup disc are on the same network, and that the backup disc is turned on. Then try again to back up."
The circumstances of this are as follows: TM seems to be trying to completely back up everything already backed up from previous months so I am using the "exclude" option to do this in manageable chunks (5.54TB of 7.99TB is available so there is a lot of stuff on there, hence my reticence to erase and start again). I started a backup last night which said it was 242GB and when I came back hours later (I estimate 30GB and hour or 500MB a minute) it has failed with the error message above. I asked it to back up again and it said it now had 191GB to backup, at the next failure it was 142GB, dropping by approx 50GB a time (if there a maximum it can manage in one go?), the next time it was starting again with 242GB.
I checked the disc it was backing up to, discovered it was now selecting Public-1, re-selected Public which houses the macpro.sparsebundle, dropped the backup size (Options) to 73GB and set it off again and it is backing up as I write. I am hoping it will complete and permit another chunk to be backup but the fact it looses network connection (seemingly) or has a maximum backup in one go, is annoying because it means you cannot leave it overnight and trust it to do the backups.
The other problem seems to be a shut down by LaCie 5Big because several times (and once this morning) I have had this message "The file server "LaCie 5Big" has closed down, followed by a complete Lacie shut down and auto-reboot with all lights and whistles. Lacie think this could be a power supply problem and say they are sending me another power brick. They also say they do not support Time Machine (they should check their own literature) and suggest I use LaCie 5Big for 'drag and drop' backup. If I wanted to do that I could pick up a cheap and nasty HD from PCWorld, not this high end 10TB drive which cost over £1,000 !
For a while y'day I could not even find the Lacie on the network but after changing the ethernet cable from Lacie to router (Linksys) it miraculously re-appeared so that problem may have been the original Lacie blue ethernet cable had developed a fault. Checking cables is an oft-overlooked option.
A catalogue of errors, some solved, others still all pervading, so any words from the wise would be gratefully accepted.

I verified the macpro.sparsebundle and Time Machine backups in Disk Utility and it said both appeared to be Okay in green type. So that did not solve the issue. I did a Disk Utility repair a day or so again (despite Verify saying everything was fine) and said there was nothing to repair. I suspect two problems, the power brick may be faulty producing intermittent power and maybe causing the drive to close down (hopefully Lacie will send me a replacement to try) and second, I am thinking the network connection is getting dropped causing crashed backups without the Lacie shutdown/reboot sequence. The 73GB back up failed, I started it again at 54GB and it failed again, just started it again at 45GB - this is no way to progress!
Perhaps the relatively new (last year) Linksys router is the problem, I find my MBP says AirPort is active but it fails to appear in Go>Server unless I switch it off and on again and perhaps a similar problem drops the connnection to the Lacie.

Time Machine Failure - Unable to create backup directory

I've been using time machine for months with no problems. It seems like since I went to the 10.5.2 update I started having problems.
Time machine fails and says a problem occurred creating a backup directory. I'm running an external drive formated to the MAC Extended Journeled. I also set my computer share name with no punctuation and no spaces.
Today I got the failure and I ran repair disc in disk utility and it could not repair the disk. So I erased it, rebooted and reconfigured time machine.
Started running the backup and about 30 minutes into it stopped with the same error.
Any thing I can try?

Seems I have same problem, I came here for the answer, only to find there appears to be none!
I started off with a new 250Gb internal drive, 50 "Real" Gb to Boot Camp, rest to Mac. Re-installed from original Apple install disks to TIGER, then upgraded to LEOPARD with the Apple upgrade disk that came with the machine as an uninstalled upgrade. All firmware and software updates up to date.
First tried a Maxtor 4+ ext 750Gb Firewire drive for Time machine, 400Gb to Time Machine, other partition for other stuff. Every backup failed with Time Machine, same as the unfortunate gentleman in the pages above. Super-Duper backup to that same drive/partition worked perfectly.
So I bought a 250Gb 2.5" Western Digital drive, put it in a USB/Firewire case and tried that, but every time same problem. It would stall once 123.85Gb of 143.8Gb completed, and get no further. After a few days a reboot or forcequit was needed to stop the process, and on attempting to restart time machine later would only get to about 32kb and fail stating there was not enough space on the drive. (123Gb already backed up, only 19Gb to go, and 106Gb free on the backup drive)
I have re-formatted (Standard Mac extended/journalled format) the drive several times now, and always same result. I have checked the drive, repaired it, and written it over with Zeroes after formatting even, still same resuly, exactly 123.85Gb into the backup it stops and goes no further. I have tried with both the firewire, and the USB plugged into the drive, same result. Time Machine does not even have the courtesy to report which file it got stuck on, so that I could manually delete it if that was the problem. Anyone found the answer to this yet?

Time Machine fails intermittently to start backup

Similar Messages

Maybe you are looking for