Time Machine hanging, I/O error

Hi, I'm having problems with Time Machine hanging partway through a backup to an external Firewire HD. I've tried repartitioning the drive, turning off Spotlight. I tried zeroing out the partition that I'm trying to back up into and ended up with Disk Utility hanging. Does this mean, as I suspect, that the drive is dying?
A sample of Console output during attempted backup looks like this:
4/30/14 7:52:30.000 PM kernel[0]: disk1s3: I/O error.
4/30/14 7:53:00.000 PM kernel[0]: disk1s3: I/O error.
4/30/14 7:54:22.000 PM kernel[0]: IOSCSIPeripheralDeviceType00::setPowerState(0xdc880163fa41ee73, 3 -> 2) timed out after 102005 ms
4/30/14 7:56:04.000 PM kernel[0]: IOSCSIPeripheralDeviceType00::setPowerState(0xdc880163fa41ee73, 2 -> 4) timed out after 101973 ms
4/30/14 7:57:30.000 PM kernel[0]: disk1s3: I/O error.
4/30/14 7:57:30.151 PM com.apple.backupd[326]: Copied 92.12 GB of 170.2 GB, 879310 of 1029040 items
4/30/14 8:03:05.000 PM kernel[0]: disk1s3: I/O error.
4/30/14 8:03:35.000 PM kernel[0]: disk1s3: I/O error.
While trying to zero out the partition I got similar messages:
5/1/14 3:32:06.468 AM fseventsd[48]: read_disk_log: problems with history file: /Volumes/Backup Partition/.fseventsd/000000000072fd18 (fd -1, errno 5 ; is_reg 0; uid 0/0 gid 0/0)
5/1/14 3:40:52.866 AM Google Chrome Helper[638]: Process unable to create connection because the sandbox denied the right to lookup com.apple.coreservices.launchservicesd and so this process cannot talk to launchservicesd. : LSXPCClient.cp #426 ___ZN26LSClientToServerConnection21setupServerConnectionEiPK14__CFDictionary_bl ock_invoke() q=com.apple.main-thread
5/1/14 3:40:52.867 AM Google Chrome Helper[638]: Process unable to create connection because the sandbox denied the right to lookup com.apple.coreservices.launchservicesd and so this process cannot talk to launchservicesd.
5/1/14 3:40:52.881 AM Google Chrome Helper[638]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1100)
5/1/14 3:42:02.821 AM ntpd[118]: ntpd: time set -0.525679 s
5/1/14 3:42:02.858 AM com.apple.time[235]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
5/1/14 3:57:36.000 AM kernel[0]: disk1s3: I/O error.
5/1/14 3:58:06.000 AM kernel[0]: disk1s3: I/O error.
5/1/14 3:58:36.000 AM kernel[0]: disk1s3: I/O error.
5/1/14 3:59:06.000 AM kernel[0]: disk1s3: I/O error.
Thanks in advance for any help.

Hi Tom, Mr. Fore,
Thanks for your quick replies. I thought since I had the Canon on its own port it would avoid the conflicts noted in the forum, but if there's only one bus that would explain things. Bummer. It's too much of a nuisance to move large files around so capturing to the internal HD isn't a long-term solution even if I got it working (that still produced the timecode problem).
I guess I have two weeks to search for a fix or a new camera before the store return policy expires.

Similar Messages

I have been using time machine to back up my Mac Book Pro 3.1 to my Time Capsule. Now the Time machine hangs up on "calculating time remaining".

I have been using time machine to back up my Mac Book Pro 3.1 to my Time Capsule. Now the Time machine hangs up on "calculating time remaining".
Mac Book Pro - 3.1-15-inch 2.4/2.2GHz), Processor 2.2 GHz Intel Core 2 Duo
Operating system : OS X 10.10.1
Time Machine Version 1.3, Copyright 2007-2014 Apple Inc., Modified Tuesday, September 9, 2014 at 6:03 PM
Time Capsule: 500 GB C 2007
This Time Machine software worked satisfactory until Monday Nov, 10 2014 and I have backups until that time. For several years, the software deleted the oldest back up to save the latest one. This is acceptable to me as I have off site storage that is updated every 3 months. How do I get Time machine working again?

I have spent a couple of days trying to respond to Linc Davis. Finally I figured it out . The following is a copy of data from my console from the initiation of a time machine backup until it gets stuck trying to calculate the time remaining. There is no indication that anything starts saving. I copied about 3 minutes of data. This is probably way too much data, but I do not know what is relevant.
Thanks for the help,
calcool
12/22/14 3:16:54.655 PM com.apple.backupd[551]: Starting manual backup
12/22/14 3:16:55.057 PM com.apple.backupd[551]: Attempting to mount network destination URL: afp://”name”%20”lastname”@Home%20Network%20Time%20Capsule._afpovertcp._tcp.loca l./Time%20Capsule
12/22/14 3:16:57.262 PM mds[33]: (Volume.Normal:2464) volume:0x7fed5ab54000 ********** Bootstrapped Creating a default store:0 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/Time Capsule
12/22/14 3:16:57.565 PM com.apple.backupd[551]: Mounted network destination at mount point: /Volumes/Time Capsule using URL: afp://”name”%20”lastname”@Home%20Network%20Time%20Capsule._afpovertcp._tcp.loca l./Time%20Capsule
12/22/14 3:17:08.000 PM kernel[0]: hfs: mounted Backup of “name” “lastname”’s MacBook Pro on device disk3s2
12/22/14 3:17:09.625 PM com.apple.backupd[551]: Disk image /Volumes/Time Capsule/”name” “lastname”’s MacBook Pro (2).sparsebundle mounted at: /Volumes/Backup of “name” “lastname”’s MacBook Pro
12/22/14 3:17:11.112 PM com.apple.backupd[551]: Backing up to /dev/disk3s2: /Volumes/Backup of “name” “lastname”’s MacBook Pro/Backups.backupdb
12/22/14 3:17:24.931 PM “name”[593]: audit warning: soft /var/audit
12/22/14 3:17:24.944 PM “name”[594]: audit warning: allsoft
12/22/14 3:17:24.958 PM “name”[596]: audit warning: closefile /var/audit/20141222201654.20141222201724
12/22/14 3:17:26.544 PM com.apple.backupd[551]: Event store UUIDs don't match for volume: Macintosh HD
12/22/14 3:17:34.767 PM com.apple.backupd[551]: Deep event scan at path:/ reason:must scan subdirs|new event db|
12/22/14 3:17:34.768 PM com.apple.backupd[551]: Reading cached event database from: /Volumes/Backup of “name” “lastname”’s MacBook Pro/Backups.backupdb/”name” “lastname”’s MacBook Pro (2)/2014-12-22-151726.inProgress/F85FEA51-E137-471A-84DA-A2C00E4ECB42/.1BEF88C6 -20C3-3DDC-AE30-05EAB2AFCC15.eventdb
12/22/14 3:17:38.115 PM com.apple.backupd[551]: Using cached disk scan
12/22/14 3:17:39.114 PM com.apple.backupd[551]: Saved event cache at /Volumes/Backup of “name” “lastname”’s MacBook Pro/Backups.backupdb/”name” “lastname”’s MacBook Pro (2)/2014-12-22-151726.inProgress/5BC46A53-25E8-4C4A-8947-AFB221D1FA0C/.1BEF88C6 -20C3-3DDC-AE30-05EAB2AFCC15.eventdb
12/22/14 3:17:39.355 PM com.apple.backupd[551]: Not using file event preflight for Macintosh HD
12/22/14 3:19:14.782 PM CoreServicesUIAgent[294]: unexpected message <OS_xpc_error: <error: 0x7fff77befc60> { count = 1, contents =
"XPCErrorDescription" => <string: 0x7fff77beff70> { length = 18, contents = "Connection invalid" }
}>
12/22/14 3:20:15.207 PM locationd[182]: Location icon should now be in state 'Active'
12/22/14 3:20:17.267 PM locationd[182]: Location icon should now be in state 'Inactive'
12/22/14 3:20:17.884 PM locationd[182]: Location icon should now be in state 'Active'
12/22/14 3:20:18.483 PM sandboxd[296]: ([310]) com.apple.metada(310) deny mach-lookup com.apple.cfnetwork.cfnetworkagent
12/22/14 3:20:21.646 PM com.apple.metadata.SpotlightNetHelper[310]: [SLSUGGESTIONS] Location managed failed with error Error Domain=kCLErrorDomain Code=0 "The operation couldn’t be completed. (kCLErrorDomain error 0.)"
12/22/14 3:20:23.892 PM WindowServer[143]: disable_update_timeout: UI updates were forcibly disabled by application "Spotlight" for over 1.00 seconds. Server has re-enabled them.
12/22/14 3:20:26.526 PM WindowServer[143]: common_reenable_update: UI updates were finally reenabled by application "Spotlight" after 3.63 seconds (server forcibly re-enabled them after 1.00 seconds)
12/22/14 3:20:28.298 PM sandboxd[296]: ([310]) com.apple.metada(310) deny mach-lookup com.apple.cfnetwork.cfnetworkagent
12/22/14 3:20:29.094 PM com.apple.xpc.launchd[1]: (com.apple.quicklook[599]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.quicklook
12/22/14 3:20:30.670 PM bird[263]: Assertion failed: ![_xpcClients containsObject:client]
12/22/14 3:20:30.670 PM bird[263]: Assertion failed: ![_xpcClients containsObject:client]
12/22/14 3:20:32.294 PM com.apple.InputMethodKit.UserDictionary[600]: -[PFUbiquitySwitchboardEntryMetadata setUseLocalStorage:](808): CoreData: Ubiquity: “name”~00000000-0000-1000-8000-001B63947FCF:UserDictionary
Using local storage: 1
12/22/14 3:20:32.317 PM bird[263]: Assertion failed: ![_xpcClients containsObject:client]
12/22/14 3:20:32.769 PM locationd[182]: Location icon should now be in state 'Inactive'
12/22/14 3:20:34.580 PM Console[601]: Failed to connect (_consoleX) outlet from (NSApplication) to (ConsoleX): missing setter or instance variable
12/22/14 3:20:35.540 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
12/22/14 3:20:36.388 PM com.apple.xpc.launchd[1]: (com.apple.auditd[604]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.auditd
12/22/14 3:20:36.693 PM “name”[608]: audit warning: soft /var/audit
12/22/14 3:20:36.718 PM “name”[607]: audit warning: allsoft
12/22/14 3:20:37.045 PM “name”[610]: audit warning: closefile /var/audit/20141222201724.20141222202036
12/22/14 3:20:37.438 PM bird[263]: Assertion failed: ![_xpcClients containsObject:client]
12/22/14 3:20:42.437 PM QuickLookSatellite[611]: CGSConnectionByID: 0 is not a valid connection ID.
12/22/14 3:20:42.437 PM QuickLookSatellite[611]: Invalid Connection ID 0
12/22/14 3:20:42.477 PM QuickLookSatellite[611]: CGSConnectionByID: 0 is not a valid connection ID.
12/22/14 3:20:42.477 PM QuickLookSatellite[611]: CGSConnectionByID: 0 is not a valid connection ID.
12/22/14 3:20:42.612 PM QuickLookSatellite[611]: [QL] No sandbox token for request <QLThumbnailRequest stackshot.log>, it will probably fail
12/22/14 3:20:42.613 PM QuickLookSatellite[611]: [QL] No sandbox token for thumbnail request file:///Library/Logs/stackshot.log, it will probably fail
12/22/14 3:20:42.615 PM QuickLookSatellite[611]: [QL] No sandbox token for request <QLThumbnailRequest stackshot-syms.log>, it will probably fail
12/22/14 3:20:42.615 PM QuickLookSatellite[611]: [QL] No sandbox token for thumbnail request file:///Library/Logs/stackshot-syms.log, it will probably fail

Every time I try to back up my Macbook Pro with an external hard drive using Time Machine, I receive the error of "the disk does not have enough space". I have a 500GB hard drive and only 120GB Macbook. It worked fine before the latest Maverick's

Every time I try to back up my Macbook Pro with an external hard drive using Time Machine, I receive the error of "the disk does not have enough space". I have a 500GB external hard drive and only 120GB Macbook. It worked fine before the latest Maverick's update. Any help would be greatly appreciated.

My guess would be it has created an entirely new backup of your drive when you upgraded to Mavericks.
See Here: http://pondini.org/TM/1.html
And here: http://pondini.org/TM/9.html
Peruse the whole site. There is a lot of information there.

Since upgrading to Lion, my time machine backups are failing - error message: The backup disk image "/Volumes/Jackie Scanlon's Time Caps/Jacqueline Drabczynska's MacBook.sparsebundle" could not be accessed (error -1). Any ideas?

Since upgrading my Macbook to Lion, the time machine backups are failing - error message: "The backup disk image “/Volumes/Jackie Scanlon's Time Caps/Jacqueline Drabczynska’s MacBook.sparsebundle” could not be accessed (error -1)." I have rebooted the TIme Capsule and it worked OK, but don't want to do that every time. Any suggestions? Thanks

Any new info on this?
I had the exact same problem and went crazy and spent a hecka lot of time trying to deal with my brand new 2TB Time Capsule and almost brand new MacBook Pro. Then I thought I fixed it...and I tried SO MANY things, I don't really know what did it...except taking out any apostrophe's in names of stuff that Apple puts in there...BUT...now it's back.
Grrr...

Time machine cannot find volume, error-1. Where can I fine solution for this error? Have latest updates for Airport and TM, running Lion.

Time machine cannot find volume, error-1. Where can I fine solution for this error? Have latest updates for Airport Utility and TM, running Lion.

See #C17 in Time Machine - Troubleshooting.

HT1338 Error preparing Time Machine backup disc- size error usually not being multiples of 512, encryption

Trying to encrypt Time Machine backup disc getting message - Error preparing Time Machine backup disc- size error usually not being multiples of 512, encryption.

I got the same problem.
But I think it cannot be related to not being a multiple of 512.
As when I devide the number of bytes 3.000.592.982.016 by 512 is equals 5860533168.
3.000.592.982.016 / 512 = 5860533168.
So what could be the real problem?
With kind Regards

Backups work, enter time machine "hangs"

I'm having an issue with Time Machine where the backups appear to be working fine, but if I open a folder in finder, and then "Enter Time Machine", Time Machine starts with that folder "visible" but hangs (no nav buttons work, cancel and restore don't work, and I can't "navigate folders).
The only way "out" in this case is to hit CMD-OPT-ESC, which weirdly doesn't bring up the terminate applications dialog, but simply exits Time Machine.
If I make sure that no finder windows are open when I enter Time Machine, it appears to be working fine.
To duplicate this, open your home folder, have Documents selected and enter time machine. Does your's hang at this point? (Hit CMD-OPT-ESC to leave Time Machine if it does hang).
TIA for any advice/confirmation.
Steve

It appears I may have "misspoken" a little. Time Machine hangs on entry with no default windows too, just "not as much". I can usually move around a little before it hang, but hang it does.
One side note (and this may cause this thread to be moved to a Leopard issue instead of time machine.
I recently upgraded to Leopard by buying a brand new drive, installing Leopard from scratch, and gradually adding back my applications as I find I need them (the previous drive had been through 10.1 -> 10.4.11 over a couple years, and had a lot of old apps, etc I just wanted to get rid of.)
With the new installation, it appears that occasionally (30% of the time?), when I mount/dismount .dmg images or sparseimage/sparsebundle images, the entire Mac will appear to "hang" for about 30-40 seconds, buffering input but otherwise appearing to "lock up". I have iTunes playing, and songs continue uninterrupted, but I can't do anything for this 30-40 seconds, including CMD-OPT-ESC.
I'm thinking this could be related to the Time Machine issue except for the fact that the OS always recovers and continues normally after 30+ seconds, but Time Machine NEVER comes back.
Thoughts? Advice?
Thanks,
Steve

Some iPhoto pictures missing after time machine recovery, were there errors reported during backup that I missed?

Hello. I used time machine/time capsule to automatically back up my sytem over the last 3 years and I used the backups to recover my system to a new hard drive when the original drive began to fail. After recovery, I noticed there are missing photos in iPhoto.
I'm curios where I should look to see why they weren't backed up, and why it wasn't obvious to me at the time that they weren't backed up.
Does time machine explicitly call out issues when it can't back up a file or does it just squirrel a message away in the system log?
I'd like to know because I'd like avoid this issue going forward.
Full disclosure & History -
The hard drive on my late 2009 27" iMac was exhibiting issues and started to go bad. No problem I thought, I'll get a new one and recover the system from my time capsule.
The full recovery was initiated from the OS install media. Upon recovery, the system wouldn't boot. After booting from the OS install media and reinstalling the OS on top of the recovered data the system booted and seemed to retain almost everything. This may not be the best way to recover but it seemed to work.
I additionally had to:
repatch the OS
reinstall iWork
relicense MS Office (otherwise office seemed to be intact)
When I started looking through my iPhoto libraries, there were some events with no pictures (mostly the newer events). I couldn't find the pictures on the time capsule either so I'm curios if there was anyway I could have known that backups weren't completing successfully. I had run a time machine incremental backup before pulling out the old hard drive and it seemed to complete successfully so I'm at a loss. I can understand that as the hard drive began to fail, there may have been issues backing up the data, but I somehow missed it if/when the problems were reported.
Should I go through the old system logs that were backed up on the time capsule and look for backupd messages/errors? Going forward, how do I know if there are backup issues?
It took me a couple weeks to realize the drive was failing. I had noticed that the system performance was getting bad, and the system would occassionally hang. It would come back OK after a restart. I thought it was because the filesystem was getting close to full (30GB left on a 1 TB drive) so I was chasing down cleaning up some data to make more room. There were suggestions in other forums to try and keep the filesystem 10% free.
While moving data from the internal drive to a new external drive (to free up space) the system would hang. I eventually found a couple disk0 errors in the kernel log and I actually witnessed disk0 disappear while running an iostat. I'm thinking it took me too long to know the disk was going bad, and so the pictures I imported over the last 3-4 weeks may be gone.
I still have the original drive so I'll see if anything else can be salvaged from it.
Looking for some suggestions on
1) the ability to know if time machine backups are successful and are in sync with my system
2) the ability to know when there are hardware issues that I should be aware of
If you got to this point, thanks for taking the time to read through all this.
Regards,
-mike

Hi Mike,
I just saw this post and saw no one has responded. You might have figured out but in case, I wanted to let you know what I found out. I had the same problem. Hard drive failure, they installed a new one and my iPhoto pictures were missing. I couldn't find them on Time Machine either which baffled (and frustrated) me b/c I just backed up my drive and I was missing pictures from over a year ago.
I found this article and it allowed me to at least find my pictures...so they weren't lost after all.
https://discussions.apple.com/message/16029742#16029742
As for why they aren't showing up in iPhoto or Time Machine, the lady at the Mac store said it is probably an OS conflict. Which makes sense since I can see the actual pictures in the iPhoto content file (per the article mentioned above). However, I didn't have my computer with me at the store to have a Genius person help me resolve the conflict.
BUT, if you can find the pictures, then maybe you can reimport them into iPhoto? Just a thought.
Good luck!

Time Machine hangs at same point during a full system restore!

I recently had a complete crash on Mac Book Pro requiring reinstallation of Latest Leopard with Upgrade Disk. Tried to restore full system from time machine backup on time capsule, but the restore stops and does not proceed at around 37-39% complete. No error messages. On the phone with apple care, was told my back up was corrupt! Any ideas. I'm very disappointed right now, as my back ups were automatic via time machine schedule. Please help me get my system back!

Andre,
You could, by-pass the Full Restore process and do an Erase & Install and Migrate. Then no 'manual' restore will be necessary. Of course, if the installer is hanging as a certain point with a Full Restore then there is no guarantee that it won't during this process as well. But it's still worth a try.
Also, if you are dealing with many GBs of user data and multiple accounts, you could have it migrate all this over in stages using Migration Assistant, rather than in one big chunk.
*Erase, Install, & Migrate*
A final option, reserved for last resort, is to erase the hard disk, install a fresh copy of the Mac OS, and then use Migration Assistant during the installation to restore your user accounts. This is the Mac equivalent of ‘Slash and Burn’, and really should only be necessary if you require a completely fresh start.
Procedure:
Verify that your Mac has uninterrupted AC power.
For faster migration of user data, Time Capsule/AirDisk users should connect their Macs directly to their Airport device via ethernet.
Insert your original Mac OS 10.5 Leopard DVD and reboot while holding down the “C” key.
At the “Welcome” screen click “Continue”.
Click “Agree” to the user agreement.
Select you Macs internal hard disk and click “Options”.
Select “Erase and Install”.
Select “Mac OS Extended (Journaled)” for disk format. (Avoid selecting “Case-sensitive” unless you know what you are doing.)
Click “OK”.
Click “Continue”.
At “Install Summary” click “Customize” if you would like to eliminate certain Print Drivers, Fonts, or Language packages from being installed. Otherwise, click “Install”.
If you wish, you can click “Skip” when the DVD integrity check begins.
After the initial installation completes, your Mac will restart and you will see the video introduction.
At “Welcome” select your country and then preferred keyboard.
At “Do You Already Own a Mac?” you are asked “Would you like to transfer your information?”
+from another Mac+
+from another volume on this Mac+
+from a Time Machine backup+
+Do not transfer my information now+
Select “from a Time Machine backup” and click “Continue”.
At “Select a Backup Volume” choose your Time Machine backup disk and click “Continue”. (If you are attempting the migration wirelessly, then click “Join...” and select your network first.)
At “Transfer Your Information” check all the categories you wish to migrate over. If you wish your Mac to be in the same state as your last backup, then check everything. Give the installer time to calculate sizes.
Once that is complete, the “Transfer” button will become active and you can click it.
After the install, verify the registration information, click “Connect” and you are done.
After logging in, immediately go to System Preferences --> Time Machine, and turn “OFF” backups, even if a backup attempted has begun.
Next, Launch Disk Utility, select your Macs’ internal disk on the left, and click “Repair Disk Permissions”.
Interestingly, no Spotlight indexing appears necessary, so, once the permission repair is complete, turn Time Machine back “ON” in the Preferences. Time Machine should continue to backup to the same set of backups that it did prior to the restore. However, due to event logs being out of sync, the first backup will require a lengthy session of “Preparing...” as Time Machine performs a “deep traversal”. Allow this to proceed uninterrupted. Naturally, the first backup after a significant installation like this will be quite large so don’t be alarmed.
Let us know if this was helpful.
Cheers!

Time Capsule and Time machine hangs my mac

I read through the first 20 pages to see if anybody else was having similar issues but then gave up so apologies if this is repeated.
OK here goes. I bought a TC 1 TB plugged it in, worked no problem and did so for ages. None of the problems mentioned by other people.
Recently I had a backup fail. At the time I had installed time machine editor some time previously and set it to back up once a day which it had been doing with no issues for weeks.
Reading the help topics I re-selected the TC in TM and off it went preparing - backup failed. Restarted both Mac and TC and tried again. This time it started the backup got to about 70GB and hung my mac - nothing worked had to hold the power button on the mac to get it to restart.
Plugged my mac directly into the TC to get a GB connection. Deleted the TC drive and reselected it. 70 (ish) GB failed and hung my machine. Checked the logs found the same file failing, excluded it from backups, deleted the drive started again - 70 ish GB failed again hung machine.
Rand apple support, was asked to do a few things. First hard reset the TC, second check permissions and repair on the mac hard drive. Third re-index the mac HD - then delete the TC drive and start again. 70 GB mac hung - warning server disconnect - backup failed.
Restarted TC and Mac, deleted TC drive, start again, 70 GB fail.
Now, the only thing that is going through my mind and im reaching here a bit is that about the time I started having problems was the same time I bought the new expansion to a game - World of Warcraft. I do play this daily and have been during the backups, I have been keeping an eye on the backups while playing and although they do appear to stop incrementing the machine is fine until I try to exit WoW. When I do the machine hangs (only does this when TM is running).
I am running out of ideas now, seem to have tried everything backups constantly failing at around the 70GB mark no more files needing to be excluded, the errors seem to be losing connection to TC server.

I ended up with a few days of talking to Apple support about this and here is how it went and this is what we tried.
Managed to get the TM to backup a full backup. The next backup failed and after that could not mount the bundle.
Deleted the drive started again, hung around 80% - same problem.
Deleted and renamed the drive - this seemed to work and full backup completed. Next backup failed.
Removed all of the 'offending' items from backup - i.e. pretty much anything that had ever been mentioned in a support forum, e.g. parallels drives, Aperture loads of stuff - no difference.
Complete reset on old time capsule - held reset button for 20 seconds while plugging power in. Deleted and renamed the old drive. Re-installed the firmware.
I excluded almost everything on the mac hard drive to make for a quick backup. It backed up fine but failed on next backup at which point the sparse bundle could no longer be mounted.
Apple still thought the problem was not the TC but something it was trying to backup.
Re-installed OSX. Removed everything from backup - i.e. excluded everything so it had nothing to backup. Then gave it 1 file to backup.
Backed up fine then failed at next backup.
Apple sent me a new replacement TC - removed everything (except parallels drive) from exclusions - plugged it in selected it as destination has been working fine ever since.
Now, Apple sent me the replacement with a not saying do not return old faulty equipment. So I got a new shiny replacement and my problem is solved.... however I am a curious sort and cannot figure out what is wrong with the old one. Its network is fine, I can use the drive as an external drive no problem (i.e. plug it in and mount the drive by connecting to server) but TM fails if I try to use it for TM backups.
The machine is a NAS, what I am trying to figure out is where is the NAS software held? is this part of the build of the harddrive or part of the firmware?
The reason I ask is, you cannot reformat a TC, only delete the network drive you create with various setting for secure delete. BUT, if you look at a TC drive it is NOT the full size of the drive within the TC. Also, there are at least 3 partitions on the drive, So I assume that the other 2 are the NAS side of things. My opinion is that one or both of the NAS partitions is corrupt, but we have no method of rebuilding these and no method of reformatting the entire disk.
I have read that you can remove the TC drive and reformat it using disk utility, but what happens when you put it back in? is it still a TC? does it still have the TC NAS functionality?
What I think is missing here is something in Airport utility that allows you to rebuild a TC from scratch. I assume the reason it isnt there is to ensure that people can't build their own TC's and have to buy Apple's, but surely Apple could build this into Airport utility so that it recognises a genuine TC and allows a re-build and/or re-format?
I am going to continue messing with the old one, to see if it can be fixed, if not it will either become the most expensive airport extreme I won or at least a Network attached disk for my PC's.

Time Machine hangs here every time

I am running Leopard 10.5.2 on a new 24 inch iMac. I have prepared a lacie 500 gb disk correctly for TM (Guid, Journaled, partition), but every time TM hangs. All Console is telling me is:
My-iMac mdworker[411]: Error: image is not of a supported color model
I have excluded .Trash and even iTunes library. What else can I do???
Any help appreciated. TM is driving me crazy.
John

• Go to the Partition tab. Create two partitions. Under Options, select GUID Partition Table (what you would use to make a Mac OS boot disk) and click OK then Apply.
• Once your partitions are in place, do it again, reverting back to just one partition, but still keeping the GUID Partition Table option. Click OK and Apply again, and at this point you should be cool.
• To be safe, you can then go to Erase and set formatting for Mac OS Extended (Journaled), then format it once and for all. But when you get there, you will probably see that your volume is already formatted in the right way.
http://gizmodo.com/gadgets/apple/leopard-disk-utility-format-issue-screws-with-t ime-machine-but-theres-an-easy-fix-316573.php

Time Machine hangs... Takes hours to do an incremental back up

Hello All,
I'm having trouble with Time Machine as of late. It seems to hang and not finish a backup (I'm not talking about the initial back up, I know they take a while).
I leave my MBP running all the time (fans are on to keep it cool, over heating not an issue) and I've noticed that after the 4th day all bets are off on a reliable backup. Usually it waits till the 2 week mark then freaks out but now it's happening more often and sooner.
I'll refrain from expressing my opinion as the Apple people don't seem to like freedom of speech as my last post got flagged when I expressed my displeasure with Snow Leopard. I'm having a lot of problems that I didn't have before the upgrade.
To the Apple people, THIS IS A REAL ISSUE I'M HAVING; note the opening statement explaining my problem. Please don't remove my post again unless you're going to contact me with how to fix it. This should not be considered "Feed Back" as I'm asking my fellow OSX users for help. Thank you!
Thank you for any advice or tips on how to fix the problem.

EricB73 wrote:
I'll refrain from expressing my opinion as the Apple people don't seem to like freedom of speech as my last post got flagged when I expressed my displeasure with Snow Leopard.
Your best bet is to omit opinions, especially negative ones. Mainly because they don't help us help you. And if they don't get deleted, many of us who try to help people just skip them, as the posters often are more interesting in ranting than working through a problem. And "freedom of speech" doesn't apply here -- this is not a government throwing you in jail, it's Apple saying you agreed to certain terms and conditions when you signed-up to use the forums they provide at no cost. Like it or not, those are the rules.
That said, you can use the Time Machine Buddy to navigate back a few days in your logs. Use the small navigation arrows after the title "Messages;" the arrow in front will show or drop the message detail. If you can find the most recent backup that was a problem, copy and post the messages here.
Do the sizes of the backups seem reasonable, considering what you've added or changed since the last one? If they seem too large, that may be part of the problem. See #D4 in the Time Machine - Troubleshooting *User Tip* at the top of this forum.
You might also try the things in #D2 of that Tip.

Time Machine And Repair Permissions Error

Hi.
I have a new Intel Mac running Leopard. "Set up Assistant" worked like a charm and brought over all my preferences, iTunes, iPhoto etc. with out a hitch. Verified permissions and the disk and came up clean.
I bought a USB LaCie 500GB external hard drive and connected it up with the idea that I would eventually use it for Time Machine.
First thing after connecting up the new hard drive, Time Machine came up and asked if I wanted it to use the new drive as a Time Machine drive and I clicked on "cancel." Thanks to all of you I knew enough to need to GUID partition and re-format the hard drive, from the FAT 32 that it came with to Mac OS Extended (journaled) that Time Machine needs. After completing this, again, the dialog box popped up about activating Time Machine and I cancelled it again.
I have not, yet, activated Time Machine. But running permission verify and repair yielded this error message both times: Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
This is the same message seen on so many other people's machines and posted here when they run into problems with Time Machine. If I don't resolve this error, will I, too, have problems running Time Machine?
This is so weird. The only thing I did between the clean permissions verification and the one with the error was connect the USB LaCie hard drive and partition and and re-format it. Time Machine has not yet been activated on this machine.
What does this SUID warning mean? Is this something I need to worry about? Should I wait to start using Time Machine?
Or... is this not a problem but there are other things I need to do to insure a good running of Time Machine?
Thanks so much for any advice you can offer.-Charlotte

The SUID is nothing to worry about.
It is documented from Apple stating this.
Everyone of us has that error.
It has not bothered Time Machine from doing its thing.

Time Machine and file system errors?

Hardware:
- 15" MBP 2GHz (mid 2006) 10.5
- WD MyBook Premium 320gb
Problem:
Time Machine backs up to a partition on the MyBook (drive is GUID partition table, partition is Mac OS Extended). Immediately after a TM backup to a reformatted partition, Disk Utility may or may not detect invalid sibling links, invalid key lengths, or other errors. If it does not detect them after the initial backup, subsequent backups of recently changed files will cause said errors. This is consistent; its occurrence is not a "maybe".
Disk Utility cannot fix these errors. fsck_hfs has had success in fixing these errors once. As I type fsck_hfs is running a second time, so we'll see the results from that. The first run produced the following:
fsck_hfs -ypr /dev/disk1s2
*Invalid node structure*
(4, 44282)
*Invalid volume file count*
(It should be 832071 instead of 802858)
*Invalid volume directory count*
(It should be 181916 instead of 177095)
*Invalid volume free block count*
(It should be 13931374 instead of 14042565)
*Volume Header needs minor repair*
(2, 0)
Questions:
- Of what is this behavior indicative?
- Is the MyBook necessarily bad?
- Is TM somehow the cause?
- Could bad sectors on the MyBook be the cause?
- Is the drive within the MBP the source of these problems (Disk Utility has not previously found any errors...)?
I'm really at a loss...

Boot from the OS X installer disc that came with the computer. After the chime press and hold down the "D" key until the diagnostic screen appears.
Booting From An OS X Installer Disc
1. Insert OS X Installer Disc into the optical drive.
2. Restart the computer.
3. Immediately after the chime press and hold down the "C" key.
4. Release the key when the spinning gear below the dark gray Apple logo appears.
5. Wait for installer to finish loading.

My Time Machine keeps repeating the error message "Time Machine could not complete the back- The back-up disk image "/Volumes/Data/User's iMac.sparsebundle" could not be accessed (error -1). How can I fix this?s/

My Time Machine could not complete the back-up. The error message says "The backup disk image "/Volumes/DataUser's iMac.sparsebundle" could not be accessed (error-1). How can I fix this problem?

Welcome to the Apple Support Communities
See > http://pondini.org/TM/C17.html

Time Machine hanging, I/O error

Similar Messages

Maybe you are looking for