Time Machine hangs at around 50GB - 60GB on initial backup
Everytime I try to create an initial back up of my MacBook Pro using my Western Digital My Book Studio through Time Machine it progresses to around half way and then stays there no matter how long I leave it. I have left Time Machine running for over night and for over 24 hours and it still hangs. I have updated firmware on hard drive and disabled indexing on Macintosh HD within system preferences.
I have scoured google and forums in an attempt to find a solution but nothing seems to be within my capabilities as my tech skills are basic. I don't want to call Apple as it appears to cost to set up a tech support call.
Any advice or solutions?
This drive is connected over Firewire 800 and my operating system is 10.7.2.
Similar Messages
-
Time machine doesn't honor exclusion list for initial backup
Hi all,
Have a MacBook Pro with Max OS X v 10.6.7 and 1 TB Time Capsule, where around 500 GB are already used for some files. For the initial Time Machine Backup I want to exclude my home directory, because it is quite large (around another 500 GB). Time Machine estimates around 32 GB for the Backup. I click on Backup Now and a couple of hours later I see still activity and has already backuped some 100s of Data including my home until it reaches the full space of the Time Capsule and crashes.
So my question is why does Time Machine does not honor my exclusion list, especially for the inital backup ?
kind regards, thomasHi, downloaded also the Combo, which seems not be entitled for my MacBook Pro, which is a brandnew one with thunderbolt.
as this german description will tell not that much, these are the both files I tried
iTomMacBookPro:Downloads turbotiga$ ls -al M*.dmg
-rw-r--r--@ 1 turbotiga staff 386096795 21 Mär 17:14 MacOSXUpd10.6.7MBPEarly2011.dmg
-rw-r--r--@ 1 turbotiga staff 1056039272 21 Mär 17:14 MacOSXUpdCombo10.6.7.dmg
still no success ... Anyway as I have installed the OS from scratch with the 2 CDs two weeks ago without any issues I still wonder, what could cause the problem ... I mean, if in the property files the exception would not be there, I would think there is an issue ... but that's not the case.
As you see in the log everything looks good
iTomMacBookPro:2011-06-19-222425.inProgress root# cat .Backup.330207865.713754.log
2011-06-19-22:24:25 - Starting backup
Previous snapshot:
None
Will traverse "Macintosh HD" (mount: '/' fsUUID: 7AD08EB2-BA93-3999-B150-6E5758282CE7 eventDBUUID: F0A21238-5A2E-4FA5-93D9-7B2CA7DCD599)
=== Starting backup loop #1 ===
Will use FirstBackupCopier
Running preflight for "Macintosh HD" (mount: '/' fsUUID: 7AD08EB2-BA93-3999-B150-6E5758282CE7 eventDBUUID: F0A21238-5A2E-4FA5-93D9-7B2CA7DCD599)
Excluding /.Spotlight-V100: 477.4 MB (86 items)
Excluding /.Trashes: 0 bytes (0 items)
Excluding /.fseventsd: 3.3 MB (358 items)
Excluding /.hotfiles.btree: 64 KB (0 items)
Excluding /Users/Shared/SC Info: 208 KB (0 items)
Excluding /private/var/db/efw_cache: 4 KB (1 items)
Excluding /private/var/db/Spotlight: 0 bytes (1 items)
Excluding /Volumes: 4 KB (2 items)
Excluding /Network: 0 bytes (0 items)
Excluding /.vol: 0 bytes (0 items)
Excluding /cores: 0 bytes (0 items)
Excluding /private/tmp: 4 KB (5 items)
Excluding /private/tftpboot: 0 bytes (0 items)
Excluding /private/var/folders: 233.5 MB (173 items)
Excluding /private/var/run: 60 KB (18 items)
Excluding /private/var/tmp: 20 KB (4 items)
Excluding /private/var/vm: 4.1 GB (2 items)
Excluding /private/var/db/dhcpclient: 8 KB (3 items)
Excluding /Library/Caches: 424 KB (14 items)
Excluding /Library/Logs: 14.0 MB (40 items)
Excluding /System/Library/Caches: 20.6 MB (22 items)
Excluding /private/var/log: 9.6 MB (101 items)
Excluding /private/var/spool/cups: 8.2 MB (14 items)
Excluding /private/var/spool/fax: 0 bytes (0 items)
Excluding /private/var/spool/uucp: 0 bytes (0 items)
Excluding /private/var/db/dyld: 406.9 MB (11 items)
Excluding /Users/turbotiga/Library/Calendars/Calendar Cache: 112 KB (1 items)
Excluding /Users/turbotiga/Library/Mail/Envelope Index: 3.9 MB (1 items)
Excluding /Users/turbotiga/Pictures/Bibliothek iPhoto/AlbumData.xml: 8 KB (1 items)
Excluding /Users/turbotiga/Pictures/Bibliothek iPhoto/iPod Photo Cache: 0 bytes (0 items)
Excluding /Users/turbotiga/Pictures: 13.1 GB (10357 items)
Excluding /Users/turbotiga/Documents: 84.0 GB (44150 items)
Should copy 713920 items (32.2 GB) representing 8446828 blocks of size 4096. 113138003 blocks available.
Preflight complete for "Macintosh HD" (mount: '/' fsUUID: 7AD08EB2-BA93-3999-B150-6E5758282CE7 eventDBUUID: F0A21238-5A2E-4FA5-93D9-7B2CA7DCD599)
Time elapsed: 26.969 seconds
Processing preflight info
Space needed for this backup: 38.7 GB (10136193 blocks of size 4096)
Finished processing preflight info
Copying items from "Macintosh HD" (mount: '/' fsUUID: 7AD08EB2-BA93-3999-B150-6E5758282CE7 eventDBUUID: F0A21238-5A2E-4FA5-93D9-7B2CA7DCD599)
iTomMacBookPro:2011-06-19-222425.inProgress root#
and then something goes wrong in paradise ... -
Time Machine said it would take 16 days to do an initial backup, and indeed, after many days it is less than a quarter done. (The problem started when I put in a new bank disk for Time Machine to write to for its backup file.)
Activity Monitor shows that the process name is backups with Process ID 6060.
Then putting this PID in Terminal UNIX command ps gave:
EdsMacPro-1:~ ed$ ps -l -p 6060
UID PID PPID F CPU PRI NI SZ RSS ...
0 6060 1 1004004 0 33 0 2556488 29040 ...
Wow! A priority of 33!
Don't know how that happened, but the way to fix that (I thought) is with renice.
But renice doesn't work.
After a lot of playing with renice and ps, it looks as though renice can not make the priority better than (no less than) 15.
And the parameter you put in, that according to the man page that is supposed to be priority, turns out to be "nice index", with priority changed by sometimes subtracting or sometimes adding either this number or twice this number - down to a limit of priority no less than 15.
EdsMacPro-1:~ ed$ ps -l -p 6060
UID PID PPID F CPU PRI NI SZ RSS ...
0 6060 1 1004004 0 33 0 2556488 29040 ...
EdsMacPro-1:~ ed$ sudo renice 5 -p 6060
EdsMacPro-1:~ ed$ ps -l -p 6060
UID PID PPID F CPU PRI NI SZ RSS ...
0 6060 1 1004004 0 28 5 2555964 29028 ...
EdsMacPro-1:~ ed$ sudo renice -5 -p 6060
EdsMacPro-1:~ ed$ ps -l -p 6060
UID PID PPID F CPU PRI NI SZ RSS ...
0 6060 1 1004004 0 38 -5 2555964 29028 ...
EdsMacPro-1:~ ed$ sudo renice -15 -p 6060
EdsMacPro-1:~ ed$ ps -l -p 6060
UID PID PPID F CPU PRI NI SZ RSS ...
0 6060 1 1004004 0 48 -15 2555964 29028 ...
EdsMacPro-1:~ ed$ ps -l -p 6060
UID PID PPID F CPU PRI NI SZ RSS ...
0 6060 1 1004004 0 48 -15 2555964 29028 ...
EdsMacPro-1:~ ed$ sudo renice -n -5 -p 6060
EdsMacPro-1:~ ed$ ps -l -p 6060
UID PID PPID F CPU PRI NI SZ RSS ...
0 6060 1 1004004 0 53 -20 2555964 29028 ...
EdsMacPro-1:~ ed$
This is with OSX 10.7.5 and Terminal 2.2.3 on an early 2009 Mac Pro with lots of memory.
What am I dong wrong, and any suggestions for how to fix my Time Machine process?The backup file size is 1.67 TB.*
That's across the internal bus of a 2009 quad-core Mac Pro - which is pretty fast.
Copying an hour's worth of MPEG-2 HD takes about a minute.
I do a fresh backup from scratch about once a year, and the last time it finished over night.
This time the first Time Machine backup is only about 1/5 complete after many days, and Activity Monitor shows essentially no use of disk drives or of CPU. And in the first note I pointed out what is gleaned by using Terminal to execute the UNIX ps command. The priority of the running Time Machine process looks incorrect to me.
I could be wrong, but I think the problem is process priority, not file size.
I am unable to set priority to 0 or a negative number. Can someone straighten me out on how to do that?
[*The machine has four 1.5 TB disk drives in it plus lots of memory. Two of the physical drives are configured as one 3 TB backup drive (RAID concatanated).] -
Time Machine freezes at 74.3 MB on initial backup (pic)
http://img233.imageshack.us/img233/8425/picture1sj9.png
last night I went to bed thinking it would be very slow for whatever reason but it would get through it. this morning I woke up and it was still on 74.3 MB. if i want to stop the backup, i cant just click on the X because nothing happens. i have to physically remove the usb drive. this is a brand new 320 GB external drive that i made 2 partitions in (1 for mac 1 for windows). I have 58GB to backup but this isn't working out.I couldn't get Time Machine to work at all—tried every suggestion I saw on this discussion board, but nothing worked. (It was start the first backup, but not complete. The Console log reported a "Bus Error".) So I gave up. Days later my Mac crashed and I couldn't get to the Finder. It would stall either right before or right after the log in screen. To get my Mac going again I had to reformat my internal hard drive and reinstall Leopard. I then restored my files from a manual backup I had done earlier. After that I tried Time Machine again and it worked perfectly. My guess is that the directory on the Mac I was trying to back up was corrupt—and that messed up Time Machine. So my suggestion is that if you can't get Time Machine to work and none of the other suggestions work- back up your Mac by some other means, format (erase) the hard drive you are trying to back up, reinstall Leopard, restore your files, and try Time Machine again. It worked for me.
-
Time Machine has failed twice- freezes halfway into initial backup
In my first attempt, the backup "froze" half way. the progress bar would not move after several hours so I stopped the backup.
In the second attempt, I let it run as long as possible eventually failing with the message
" Unable to complete backup. An Error occurred while creating the backup directory"
I am backing up to a new GTech drive that has functioned perfectly so I don't think it is a HW problem.
Has anyone else encountered this? Any ideas?I have fixed my problem and have a succesfull initial backup!
1. deleted time machine Prefs file.
2. set SLEEP to NEVER in Energy Saver.
3. unchecked "put hard disk to sleep when possible" in Energy Saver.
4. dismount/remount backup drive.
5. start backup.
6. Success ! -
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.
SteveIt 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 -
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. -
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 -
Time Machine not happy since upgrade to 10.9. Waited three days for Time Machine to perform a backup after the upgrade. Got nowhere, backed up less that 1MB in 3 days. So erased dedicated 1 TB backup disk, re-selected as TM disk and restarted Time Machine.
My hard disk is set never to sleep. So far, Time Machine has taken four days to get to:
"Backing Up: 496.06GB of 571.26GB"
It has been stuck at this point for 24 hours. But I can hear the hard disk working constantly. Activity Monitor attributes this to a kernal process. Not sure what to do. Fear my hard disk will give up the ghost at this rate before completing a single Time Machine backup.
Anyone got any idea what I should do?
Thank you in advance.Add me to the list.
My essentially new MacBook Pro, barely used, upgraded from 10.7.2 to 10.7.5 and Time Machine became a glacier, constantly stuck on Processing.
Formatted external drive, looked promising, eventually stopped backing up. Deleted Time Machine preferences, reformatted external on another Mac and gave it a new name, plugged it in to MacBook Pro, told Time Machine to use it, zipped up to about 3GB in 3 Min. and then molasses. Better than before, currently at 12GB of 36GB in about 4 hours, but still pathetic.
As an Apple Certified Tech, have seen so many problems with Time Machine, especially the weird pausing on the initial run, hard to tell when slowness is normal or problematic.
Trying to get through to Apple Tech Support, but it being Day One of iPhone 5, can't.
Please keep this thread going and post any knowledge breakthroughs. -
Question: Why does Time Machine hang on cloned drive?
I migrated my Main HD to a faster WD Velociraptor. I used the great utility Carbon Copy Cloner to clone the drive.
After a successful clone, I renamed the orignal HD (old) and duplicated the original HDD name to the new one. I shutdown, and removed the old HDD from my MacPro, and installed the New Main HD clone in it's place and rebooted.
The system came up and all looked fine until Time Machine started to index and then deleting old Backups indication. It did this for 2 hours! I let it run overnight figuring it was cleaning old backups.
This morning it had /!\ as the icon and Failed Backup indicated.
Instead of deleting the old TM backups folder on the specific HDD I use, I just formatted it, and re-assigned it as the TM HDD. It is fine now.
So what happened? How can I prevent this? Is there some file hidden and not cloned that affects TM?Eddie Ski wrote:
This morning it had /!\ as the icon and Failed Backup indicated.
Most likely, it failed for lack of space for the new backup.
So what happened? How can I prevent this? Is there some file hidden and not cloned that affects TM?
The new drive may have all the same stuff on it as the old one, but it does have a different UUID (Universally Unique IDentifier), and that's what OSX uses to keep track of drives, not their names.
So Time Machine sees a different drive, and its whole role in life is to back up whatever's new or changed, so that's what it does. You cannot prevent it. -
Time Machine has lost the link with its old backup files
This has got me a bit puzzled.
I recently obtained a nice new iMac to use in conjunction with my trusty MacBook Pro. Previously the MBP was my main machine and I habitually plugged it into an external HDD for Time Machine to use. No problem there.
Now, since setting up the iMac I have the external HDD connected to that. I access the HDD on the MBP over my ethernet network, which is great: I can swap files, sync files easily and automatically with ChronoSync, and I'm very happy. The only problem is that I can't use the HDD for backing up the MacBook Pro anymore. Time Machine says there isn't enough room, "This backup is too large for the backup volume." Obviously TM doesn't recognise its own files from the days when the HDD was connected directly to the MBP.
I realise I can erase the HDD and tell TM to start backing up from scratch but I'm hesitant to do so. I have months of incremental backups on there already and I'm not keen to lose them. Is there anything I can do to pick up from where TM left off before I changed my cables around? It seems such a pity to throw months of backup out the window.Have you thought about re-connecting your HDD directly back to your MBP - as you had it before. Provided the MBP's name has not changed, TM should pick-up from where it left off. Bear in mind that TM will only back up one mac at a time, and as I understand it, you would need Time Capsule or other networkable HD to back up both macs to. Considering the reasonable cost of external HD, you might be better off to get another one for your iMac.
The macs can still be connected over the network and you could still use ChronoSync for syncing etc.
Joe -
I have had a series of Macs. They have been backed up with Time Machine. I am trying to restore TM backup files from the older Macs using my new MacBook Pro. No go. What do I do ?
I am trying to restore TM backup files from the older Macs using my new MacBook Pro. No go.
Migration Assistant (Finder > Applications > Utilities > Migration Assistant) is the tool that you would use to restore backups from older Macs to another Mac.
Details are here: http://pondini.org/OSX/MigrateLion.html The same info applies for Mavericks and Yosemite. If you are saying that this is a "no go".....where are you getting stuck? What error messages do you see? -
I am trying to update my time machine backup on time capsule, but time machine keeps trying to create an entirely new backup (evidenced by the 200GB backup size). How can I get time machine to modify my old backup rather than create a new one?
It must have found the old backup corrupt.. so you will more than likely have little choice. You can archive off the old backup if it is still useful.
You can also verify it. See A5 http://pondini.org/TM/Troubleshooting.html
He also has some info on this problem. eg C13. -
Time Machine warning: An error occured while creating a backup folder. What to do???
Time Machine warning: An error occured while creating a backup folder. What to do???
If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message that corresponds to an abnormal backup. Now
CLEAR THE WORD "Starting" FROM THE TEXT FIELD
so that all messages are showing, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them to the Clipboard by pressing the key combination command-C. Paste (command-V) into a reply to this message.
If all you see are messages that contain the word "Starting," you didn't clear the text field.
If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Some personal information, such as the names of your files, may be included — anonymize before posting. -
Since updating OS to Mountain Lion from leopard, I get the following error message when trying to backup with time machine on external drive. "Could not complete backup to media share. The network backup disk does not support the required AFP features." What are AFP features and how do I get Time Machine to backup to my current external backup?
This means that your NAS does not support the required encryption. Update your NAS to the latest firmware or ditch it and buy a Time Capsule (they are the most reliable when using TM).
Maybe you are looking for
-
cannot get iPad to connect to WiFi because I can't find the password-and now i can't get the iPad to reset to be able to connect through iTunes--help
-
Is there a thunderbolt to firewire 400 adaptor available?
I have an old Sony handycam (connects using firewire 400) with heaps of footage on it from years of overseas travel. When I buy my new Macbook Pro, I want to load my video into iMovie. I see there is a thunderbolt to firewire 800 adaptor, but that's
-
How to send FDF file when submitting a PDF form
Most users do not have Pro only reader. I need to be able to send the fdf file so that when the user launches the fdf file the digital signatures will be in tact and form fields populated. Is that possible?
-
Movie Purchases and 5.1 Surround
Recently I've been noticing some movies (such as Casino Royale and the just released Australia) come with 5.1 Surround Sound. When these are downloaded through iTunes, will they play in Surround on a Machine (given a proper system of course) or is it
-
Monitor settings incorrect and can't get to system prefs to change them
Hi, I was experimenting with screen resolution settings and somehow came up with one that doesn't allow me to get to any finder controls or to the apple icon. So I can't use my computer. Help!