FYI: No Sleep during Time Machine initial backup

Just an FYI - I noticed that during the first Time Machine full backup, the computer does not go to sleep.
I would also assume that if you computer is asleep, it will not wake for each hourly backup.

Hi, and welcome to the forums.
You need to know that backing-up that way is "iffy" and +*not supported by Apple.+* See Using Time Machine with an Airport Extreme Air Disk (or use the link in *User Tips* at the top of this forum).
Kernel panics are usually caused by hardware problems, but can be software.
Disconnect all peripherals, except keyboard and mouse. Reconnect one at a time to see if you can find the culprit.
If that's no help, run the Apple Hardware Test: http://support.apple.com/kb/HT1509
And perhaps a heavy-duty memory test, such as the free Rember: http://www.kelleycomputing.com/
More kernel panic info:
Apple Support - About kernel panic messages
Mac OS X Kernel Panic FAQ
The X Lab - Resolving Kernel Panics
Apple Developer - Technical Note TN2063: Understanding and Debugging Kernel Panics
Tutorial: Avoiding and eliminating Kernel panics
|
If you still want to back up via the Airport, the first backup will be much faster if you connect via Ethernet.

Similar Messages

Kernel panic during Time Machine initial backup

Hi all!
I've got the Airport Extreme 2009 and external WD My Passport 320GB attached to it via USB and shared to the LAN. While initial backup with Time Machine via WiFi my MacBook Pro gets kernel panic.
My Passport has been formatted as Extended Journaled Case-sensitive file system.
Did anybody stumble upon such problem?

Hi, and welcome to the forums.
You need to know that backing-up that way is "iffy" and +*not supported by Apple.+* See Using Time Machine with an Airport Extreme Air Disk (or use the link in *User Tips* at the top of this forum).
Kernel panics are usually caused by hardware problems, but can be software.
Disconnect all peripherals, except keyboard and mouse. Reconnect one at a time to see if you can find the culprit.
If that's no help, run the Apple Hardware Test: http://support.apple.com/kb/HT1509
And perhaps a heavy-duty memory test, such as the free Rember: http://www.kelleycomputing.com/
More kernel panic info:
Apple Support - About kernel panic messages
Mac OS X Kernel Panic FAQ
The X Lab - Resolving Kernel Panics
Apple Developer - Technical Note TN2063: Understanding and Debugging Kernel Panics
Tutorial: Avoiding and eliminating Kernel panics
|
If you still want to back up via the Airport, the first backup will be much faster if you connect via Ethernet.

Very slow Time Machine Initial Backup to Leopard Server on Xserve with RAID

I'm having trouble backing up my iMac to my Xserve running leopard with dual drobos as my time machine drives
So here is the setup:
Server: Xserve (dual quad 2.8 xeons) backing up to Drobo array with 4x1tb drives running (dual drobos on server) fully patched 10.5 server with 16gb/RAM (showing 8gb free)
Network: 1gbs via catalyst switches on essentially unloaded segment (a couple of folks reading emails)
Source Machine: iMac 24" 3.06 Core2Duo with 8gb RAM
Most important fact: nothing has changed on the server (other than usual updates)
Doing an initial backup of the iMac over the network, and getting peak of about 100Kb/sec, and much of the time it seems to have stalled. Given that the machine has like 230GB to backup, this is going to take a real long while. When I query activity monitor on both the client and Xserve, they are both virtually idle with all resources free (lots of free RAM/Disk/CPU). Neither machine is running any apps right now during the test (other than filesharing, but nobody is using as the office is empty today)
Now one thing to note is the staggering number of files (iPhoto library is ~120gb and holds over 500,000 files [faces?]) giving a total of 1.2M files.
As a point of testing, copied a 500mb quicktime movie to same partition, took <5 seconds.

Should I be concerned that the TimeMachineBuddy widget is producing tons of error messages in the system console (and doesn't seem to work)
8/4/09 3:34:01 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:01.438 DashboardClient[381:10b] com.bluedog.tmwidget.TimeMachine: ERROR: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma
8/4/09 3:34:01 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:01.439 DashboardClient[381:10b] (com.bluedog.tmwidget.TimeMachine) file:///Users/henryhbk/Library/Widgets/Time%20Machine%20Buddy.wdgt/Utilities.js: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma (line: 33)
8/4/09 3:34:02 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:02.359 DashboardClient[381:10b] com.bluedog.tmwidget.TimeMachine: ERROR: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma
8/4/09 3:34:02 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:02.360 DashboardClient[381:10b] (com.bluedog.tmwidget.TimeMachine) file:///Users/henryhbk/Library/Widgets/Time%20Machine%20Buddy.wdgt/Utilities.js: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma (line: 33)
8/4/09 3:34:02 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:02.620 DashboardClient[381:10b] com.bluedog.tmwidget.TimeMachine: ERROR: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma
8/4/09 3:34:02 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:02.621 DashboardClient[381:10b] (com.bluedog.tmwidget.TimeMachine) file:///Users/henryhbk/Library/Widgets/Time%20Machine%20Buddy.wdgt/Utilities.js: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma (line: 33)
8/4/09 3:34:02 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:02.885 DashboardClient[381:10b] com.bluedog.tmwidget.TimeMachine: ERROR: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma
8/4/09 3:34:02 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:02.885 DashboardClient[381:10b] (com.bluedog.tmwidget.TimeMachine) file:///Users/henryhbk/Library/Widgets/Time%20Machine%20Buddy.wdgt/Utilities.js: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma (line: 33)

Time Machine initial backup fails OS 10.5 with no reason but 'bus error'

I ran into an error on the last system update and had to go back to Leopard 10.5 just to see my stuff. I managed to move my home directory into the newly installed system and all my files are intact. Now I'm trying to get a Time Machine backup before I proceed (my initial mistake was not keeping up with them in the first place).
I had some trouble early on and at one point decided to reformat the external drive (a Fantom Drives GreenDrive, usb, 500Gb). I formatted as Mac OS Extended (Journaled) as recommended, no partitions, and then tried my first initial Time Machine backup.
It predictably spent a long time 'preparing...' and I followed along in the system log. Eventually, the copying began but early on (within the first 45 min) the backup failed with almost no indications in the log as to why. I've pasted the system log below.
One thought I had was that it was weird that there was an automatic request for backup at 12:36:54. I also included the CrashReport, but I can't make any sense out of it.
any ideas?
System log:
6/23/10 11:57:30 PM /System/Library/CoreServices/backupd[1190] Backup requested by user
6/23/10 11:57:30 PM /System/Library/CoreServices/backupd[1190] Starting standard backup
6/23/10 11:57:30 PM /System/Library/CoreServices/backupd[1190] Backing up to: /Volumes/Deep Green/Backups.backupdb
6/24/10 12:15:13 AM /System/Library/CoreServices/backupd[1190] No pre-backup thinning needed: 173.94 GB requested (including padding), 453.71 GB available
6/24/10 12:15:13 AM /System/Library/CoreServices/backupd[1190] MDBackupBegin() returned result (910) > 0, waiting
6/24/10 12:36:54 AM /System/Library/CoreServices/backupd[1190] Backup requested by automatic scheduler
6/24/10 12:42:17 AM ReportCrash[1431] Formulating crash report for process backupd[1190]
6/24/10 12:42:18 AM com.apple.launchd[1] (com.apple.backupd[1190]) Exited abnormally: Bus error
6/24/10 12:42:24 AM ReportCrash[1431] Saved crashreport to /Library/Logs/CrashReporter/backupd2010-06-24-004204dylan-boyds-macbook.crash using uid: 0 gid: 0, euid: 0 egid: 0
CrashReport:
Process: backupd [1190]
Path: /System/Library/CoreServices/backupd
Identifier: backupd
4 backupd 0x00007525 0x1000 + 25893
5 backupd 0x00002332 0x1000 + 4914
8 backupd 0x00015028 0x1000 + 81960
9 backupd 0x0000ea64 0x1000 + 55908
10 backupd 0x00008bfe 0x1000 + 31742
11 backupd 0x00004c10 0x1000 + 15376
12 backupd 0x000057b8 0x1000 + 18360
0x1000 - 0x3dffb backupd ??? (???) <f50411bdb241b61699aa81b2f3dfb7d1> /System/Library/CoreServices/backupd

I should have added that I've been through about half a dozen sites (including sanctioned apple sites) and their recommendations for getting Time Machine to work properly. I did format the drive once (with extended journaled format and GUID partition scheme, but I didn't zero it out. I'm trying that now and I'll try TM again in about 4 hours.
This morning I tried turning Time Machine's automatic backups off (moved the slider to off in the preferences pane) and manually started a backup (right-clicking the TM icon in the dock and selecting "Backup Now"). It ran further along than before, but stopped again. This time, it gave an error, and I've pasted the log below. I looked but didn't find much helpful on "error 11."
system log:
Jun 24 09:14:08 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Backup requested by user
Jun 24 09:14:08 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Starting standard backup
Jun 24 09:14:08 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Backing up to: /Volumes/Deep Green/Backups.backupdb
Jun 24 09:14:08 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Event store UUIDs don't match for volume: Macintosh HD
Jun 24 09:14:08 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|
Jun 24 09:47:13 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: No pre-backup thinning needed: 175.31 GB requested (including padding), 453.11 GB available
Jun 24 10:13:46 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Error: (-36) SrcErr:YES Copying /Previous Systems.localized/2010-06-22_2236/Applications/iPhoto.app/Contents/Resources/Po intOfInterest.db to (null)
Jun 24 10:13:46 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Error: (-36) SrcErr:NO Copying /Previous Systems.localized/2010-06-22_2236/Applications/iPhoto.app/Contents/Resources/Po intOfInterest.db to /Volumes/Deep Green/Backups.backupdb/Dylan Boyd’s MacBook/2010-06-23-231048.inProgress/E3294B86-62B0-4ABF-9B2B-F5D46B82736D/Macin tosh HD/Previous Systems.localized/2010-06-22_2236/Applications/iPhoto.app/Contents/Resources
Jun 24 10:13:46 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Stopping backup.
Jun 24 10:13:46 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Error: (-8062) SrcErr:NO Copying /Previous Systems.localized/2010-06-22_2236/Applications/iPhoto.app/Contents/Resources/Po intOfInterest.db to /Volumes/Deep Green/Backups.backupdb/Dylan Boyd’s MacBook/2010-06-23-231048.inProgress/E3294B86-62B0-4ABF-9B2B-F5D46B82736D/Macin tosh HD/Previous Systems.localized/2010-06-22_2236/Applications/iPhoto.app/Contents/Resources
Jun 24 10:13:57 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Copied 13360 files (1.5 GB) from volume Macintosh HD.
Jun 24 10:13:57 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Copy stage failed with error:11
Jun 24 10:14:03 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Backup failed with error: 11

Time Machine Initial Backup - Partial Only

I have a WD external drive that was erased by Time Machine. But the initial backup stops at about 1 gig of data (out of the 38 gig that is there). Then schedules another backup in an hour. Why doesn't

Hi!
Time Machine has worked for several months now but since yesterday i have the same issue. After reformatting the backup disk (file system was corrupt) time machine works but stops backing up after about 100MB.
Cheers
Silvan

Time Machine initial backup

I just used Time Machine for the first time. I expected it to backup about 35GB (and it estimated a full backup at 35.54GB) but it actually backed up 30.06GB. I looked at the Options screen and the only thing listed as "do not backup" is my backup drive which it lists as 2.52GB. Any thoughts on why the initial full backup does not seem to be the size expected?

The comment from Steve Holton i think has your answer on https://discussions.apple.com/message/7884490?messageID=7884490
In short there are some things skipped by Time Machine have a look at /Library/Preferences/com.apple.TimeMachine.plist in the ExcludeByPath

Mac enters a deep sleep during Time Machine full restore

I have the problem listed in the subject. Here is my configuration:
Mac Pro (early 2008), dual quad-core Xenon 2.8 GHz, 10 GBs of RAM, hard disks as follows:
Bay 1: 1 TB HD System, running OS X 10.6.2, ~500 gigs used, ~400 gigs free, small Bootcamp partition
Bay 2: 1.5 TB hard disk, used exclusively for backing up the drive in Bay 1
Bay 3: 1 TB spare drive, currently contains only OS X 10.6.2 plus some utilities. This drive is not backed up.
Bay 4: empty
OK, so now for what happened. Recently, I had an issue with my main drive (bay 1); rather than attempt to fix it, I decided to reformat the drive and restore from a Time Machine backup. I booted off the Snow Leopard DVD, chose the Restore option from the Utilities menu, and started the restore.
When I returned to the Mac after a couple of hours to see how things were going, the Mac was asleep and could not be woken up by moving the mouse, clicking its buttons, or hitting any key on the keyboard. The (wired) keyboard was totally inactive (no caps lock light, etc.). Pressing the Power button on the Mac Pro didn't do anything, nor could I connect to it from my MacBook Pro by means of screen or file sharing. The only thing I could do was to hold the power button in until the machine turned off completely. Restarting from the DVD worked fine.
I looked for answers on the web, and I found a couple of posts here. One of them suggested setting the sleep parameter to "Never" (if one still had a boot partition); I did that by booting from the disk in bay 3, not quite believing it would work since I was booting from the DVD to do the restore.
Once booted from the DVD, I tried the other answer I had found, and that is executing the command "pmset sleep 0" in the terminal before launching the restore. I got an error to the effect that the write operation failed (duh!), but I thought that maybe the parameter would be held in memory. I started the restore operation again and went to sleep.
Needless to say, the same thing happened again. The only way I was finally able to perform the restore was by sitting next to the machine and moving the mouse every few minutes to keep the system awake. This process took a little over two and a half hours (which is not bad considering the amount of data involved). The operation was successful, and I was able to boot from the restored drive. Everything is now back to normal. However, I am puzzled by the apparent necessity to babysit the Mac while it is restoring from a Time Machine backup.
This clearly did NOT happen with the Leopard (10.5) DVD. I suspect (but don't know for sure) that the 10.5 DVD's system included a never sleep setting that Apple forgot to include on the 10.6 DVD.
Is anybody able to perform lengthy restores by booting from the Snow Leopard DVD? If so, how do they get around the sleep issue? Or doesn't it happen in the first place? I would also like to know what state my Mac is in when it stops in the middle of a restore operation; it is clearly not a normal sleep mode since I haven't actually found any way of waking it up.
Finally, I would love to be able to boot from my Bay 3 drive and launch a system restore operation from there since both the Time Machine drive and the target drive would be available. Is there any way at all that this can be done? Has anyone succeeded in using the Time Machine full restore from any location other than the OS DVD? This would obviously be interesting since one could continue to use the Mac while the restore operation is ongoing.
Thanks for any info anyone can provide.
Daniel

something is wrong with your system. changing energy saver settings while booted normally from an external should have taken care of this issue. I suggest you reset SMC
http://support.apple.com/kb/HT3964
and you are right, using "pmset sleep 0" from terminal while booted from the DVD does not work. I think it was me who recommended that. that was very dumb of me. thanks for pointing that out. but it should not be necessary as i mentioned.
all that said, in response to your last question yes it is perfectly possible to run the installer and the restore utility while booted normally from another drive. beeing quite impatient (and having a mac pro with several internal bays ) this is the only way I ever install or restore. also, I don't use the DVD itself. I made a small partition on one of my internals and cloned the SL install DVD to that. it works much quicker from there.
anyway, to start the installer while booted normally from another drive run the following terminal command
sudo /Volumes/Mac OS X Install DVD/System/Installation/CDIS/Mac OS X Installer.app/Contents/MacOS/Mac OS X Installer
this will let you use the mac and do other things while the restore is going on.

Time machine initial backup is taking over 3 days

I have an external network drive which I am trying to back up my MacBook Pro OS X 10.6.8 to using Time Machine. Why after 2 days is the backup only 40% done? I know it can take time to set it up but... really?
I had to start over since it is a laptop computer and I do need to take it with me... but I really can't afford more than 24 hours of keeping it on the network.
What's the deal? Thanks!

https://discussions.apple.com/docs/DOC-4055

Time machine initial backup duration

How long should it take for Time Machine to make it's first full back up of data? I'm 92GB into a save of 496GB, and it's predicting 11 more DAYS of copying before it's done. I did have to stop it once, but seems to have restarted. Is this typical, or should I have just reformatted and started over? Or is this the first sign of HD failure somewhere? My HDs is WD connected via USB2, I think.
Jack

How long should it take for Time Machine to make it's first full back up of data? I'm 92GB into a save of 496GB, and it's predicting 11 more DAYS of copying before it's done. I did have to stop it once, but seems to have restarted. Is this typical, or should I have just reformatted and started over? Or is this the first sign of HD failure somewhere? My HDs is WD connected via USB2, I think.
Jack

System "hiccup" during Time Machine Backups

Over the course of the past week or so, I've noiticed that my system will freeze/stall/hiccup (whatever you call it) during Time Machine backups. This will apply to YouTube/Vimeo videos, iTunes (where I noticed it... it's like the song pauses and resumes 2 or 3 times over 10 seconds), task switching, text entry, etc. Again, this is only a recent thing.
Here's a log of what I was doing during this last backup. Didn't check the time when iTunes froze, but it happened at least twice, maybe 3 times.
3/5/13 4:50:35.477 PM com.apple.backupd[48152]: Starting automatic backup
3/5/13 4:50:36.010 PM com.apple.backupd[48152]: Backing up to: /Volumes/Hydra 1/Backups.backupdb
3/5/13 4:50:55.980 PM com.apple.backupd[48152]: Using file event preflight for Mac HD
3/5/13 4:51:18.189 PM com.apple.backupd[48152]: Will copy (2.07 GB) from Mac HD
3/5/13 4:51:19.601 PM com.apple.backupd[48152]: Found 105304 files (2.55 GB) needing backup
3/5/13 4:51:19.638 PM com.apple.backupd[48152]: 4.58 GB required (including padding), 153.96 GB available
3/5/13 4:51:53.825 PM locationd[48163]: NOTICE,Location icon should now be in state 0
3/5/13 4:52:01.241 PM lsboxd[245]: @AE relay 4755524c:4755524c
3/5/13 4:53:40.070 PM mdworker[48192]: Unable to talk to lsboxd
3/5/13 4:53:40.075 PM mdworker[48191]: Unable to talk to lsboxd
3/5/13 4:53:40.219 PM sandboxd[48194]: ([48192]) mdworker(48192) deny mach-lookup com.apple.ls.boxd
3/5/13 4:53:40.226 PM sandboxd[48194]: ([48191]) mdworker(48191) deny mach-lookup com.apple.ls.boxd
3/5/13 4:53:40.000 PM kernel[0]: Sandbox: sandboxd(48194) deny mach-lookup com.apple.coresymbolicationd
3/5/13 4:53:58.561 PM Messages[26674]: [Warning] Updating typing guid on IMMessage from 3FEF0FB8-9FEC-4C4F-93B9-ABA280016F8A to AB036A47-4BE4-4DD7-879D-1ED11CF1F0E0
3/5/13 4:54:08.903 PM iTunes[1027]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:54:08.905 PM ath[1032]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:54:11.000 PM kernel[0]: disk0s2: I/O error.
3/5/13 4:54:27.000 PM kernel[0]: disk0s2: I/O error.
3/5/13 4:54:27.526 PM com.apple.backupd[48152]: Error: (-36) SrcErr:YES Copying /Users/niclake/.dropbox/sigstore.dbx to (null)
3/5/13 4:54:52.106 PM iTunes[1027]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:54:52.108 PM ath[1032]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:55:24.726 PM coreservicesd[65]: Application App:"Sublime Text 2" [ 0x0/0x13ea3e9] @ 0x0x7ffb51e75860 tried to be brought forward, but isn't in fPermittedFrontASNs ( ( ASN:0x0-0x14d24d1:) ), so denying.
3/5/13 4:55:24.726 PM WindowServer[93]: [cps/setfront] Failed setting the front application to Sublime Text 2, psn 0x0-0x13ea3e9, securitySessionID=0x186a3, err=-13066
3/5/13 4:55:24.765 PM authexec[48213]: executing /bin/cp
3/5/13 4:55:35.752 PM KernelEventAgent[45]: tid 00000000 received event(s) VQ_NOTRESP (1)
3/5/13 4:55:35.752 PM KernelEventAgent[45]: tid 00000000 type 'afpfs', mounted on '/Volumes/Chimera', from '//Nic%20Lake@Nic%60s%20AirPort%20Extreme._afpovertcp._tcp.local/Chimera', not responding
3/5/13 4:55:35.000 PM kernel[0]: ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 575 on so 0xffffff8026cb6260
3/5/13 4:55:35.000 PM kernel[0]: ASP_TCP asp_tcp_usr_control: invalid kernelUseCount 0
3/5/13 4:55:35.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect started /Volumes/Chimera prevTrigger 575 currTrigger 576
3/5/13 4:55:35.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Chimera
3/5/13 4:55:35.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: posting to KEA EINPROGRESS for /Volumes/Chimera
3/5/13 4:55:35.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/Chimera
3/5/13 4:55:35.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Chimera
3/5/13 4:55:35.752 PM KernelEventAgent[45]: tid 00000000 found 1 filesystem(s) with problem(s)
3/5/13 4:55:35.869 PM KernelEventAgent[45]: tid 00000000 received event(s) VQ_NOTRESP (1)
3/5/13 4:55:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 13 /Volumes/Chimera
3/5/13 4:55:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Chimera
3/5/13 4:55:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: get the reconnect token
3/5/13 4:55:45.111 PM mdworker[48217]: Unable to talk to lsboxd
3/5/13 4:55:45.119 PM mdworker[48218]: Unable to talk to lsboxd
3/5/13 4:55:45.339 PM sandboxd[48215]: ([48217]) mdworker(48217) deny mach-lookup com.apple.ls.boxd
3/5/13 4:55:45.348 PM sandboxd[48215]: ([48218]) mdworker(48218) deny mach-lookup com.apple.ls.boxd
3/5/13 4:55:45.000 PM kernel[0]: Sandbox: sandboxd(48215) deny mach-lookup com.apple.coresymbolicationd
3/5/13 4:56:15.453 PM Messages[26674]: [Warning] Updating typing guid on IMMessage from 87A43B63-A4B2-4E41-B472-34083741613A to BA8D492D-6BDB-4B9B-9A44-50D21FCFAC7E
3/5/13 4:56:24.430 PM Messages[26674]: [Warning] Updating typing guid on IMMessage from 86F1F958-B235-4C5B-BCEE-537E0826534D to 2A54A84E-C80B-43F6-A31B-0148CB5367B0
3/5/13 4:56:31.437 PM lsboxd[245]: @AE relay 4755524c:4755524c
3/5/13 4:56:35.096 PM iTunes[1027]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:56:35.098 PM ath[1032]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:56:37.574 PM Messages[26674]: [Warning] Updating typing guid on IMMessage from A0CF4108-C32F-4E4C-B1FB-5745F2EFA376 to B890B725-4D5B-4338-9574-42E1BC800D26
3/5/13 4:56:53.912 PM iTunes[1027]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:56:53.914 PM ath[1032]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:57:09.327 PM iTunes[1027]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:57:09.331 PM ath[1032]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:57:48.285 PM mdworker[48246]: Unable to talk to lsboxd
3/5/13 4:57:48.291 PM mdworker[48247]: Unable to talk to lsboxd
3/5/13 4:57:48.388 PM sandboxd[48243]: ([48246]) mdworker(48246) deny mach-lookup com.apple.ls.boxd
3/5/13 4:57:48.423 PM sandboxd[48243]: ([48247]) mdworker(48247) deny mach-lookup com.apple.ls.boxd
3/5/13 4:57:48.000 PM kernel[0]: Sandbox: sandboxd(48243) deny mach-lookup com.apple.coresymbolicationd
3/5/13 4:58:13.430 PM Tweetbot[22562]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
3/5/13 4:58:25.538 PM iTunes[1027]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:58:25.540 PM ath[1032]: _NotificationSocketReadCallbackGCD (thread 0x7fff75326180): Unexpected connection closure...
3/5/13 4:58:30.819 PM iTunes[1027]: ImageIO: JPEG Corrupt JPEG data: premature end of data segment
3/5/13 4:58:30.829 PM Bowtie Butler[1030]: ImageIO: JPEG Corrupt JPEG data: premature end of data segment
3/5/13 4:59:52.515 PM com.apple.backupd[48152]: Copied 118801 files (2.47 GB) from volume Mac HD.
3/5/13 4:59:52.707 PM com.apple.backupd[48152]: Using file event preflight for Mac HD
3/5/13 4:59:53.910 PM com.apple.backupd[48152]: Will copy (3.4 MB) from Mac HD
3/5/13 4:59:53.913 PM com.apple.backupd[48152]: Found 120 files (3.4 MB) needing backup
3/5/13 4:59:53.914 PM com.apple.backupd[48152]: 1.84 GB required (including padding), 150.66 GB available
3/5/13 5:00:16.000 PM kernel[0]: disk0s2: I/O error.
3/5/13 5:00:16.222 PM com.apple.backupd[48152]: Error: (-36) SrcErr:YES Copying /Users/niclake/.dropbox/sigstore.dbx to (null)
3/5/13 5:00:35.593 PM com.apple.backupd[48152]: Copied 1349 files (53 MB) from volume Mac HD.
3/5/13 5:00:36.426 PM KernelEventAgent[45]: tid 00000000 received event(s) VQ_NOTRESP (1)
3/5/13 5:00:36.426 PM KernelEventAgent[45]: tid 00000000 type 'afpfs', mounted on '/Volumes/Chimera', from '//Nic%20Lake@Nic%60s%20AirPort%20Extreme._afpovertcp._tcp.local/Chimera', not responding
3/5/13 5:00:36.000 PM kernel[0]: ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 576 on so 0xffffff8026cb6260
3/5/13 5:00:36.000 PM kernel[0]: ASP_TCP asp_tcp_usr_control: invalid kernelUseCount 0
3/5/13 5:00:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect started /Volumes/Chimera prevTrigger 576 currTrigger 577
3/5/13 5:00:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Chimera
3/5/13 5:00:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: posting to KEA EINPROGRESS for /Volumes/Chimera
3/5/13 5:00:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/Chimera
3/5/13 5:00:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Chimera
3/5/13 5:00:36.427 PM KernelEventAgent[45]: tid 00000000 found 1 filesystem(s) with problem(s)
3/5/13 5:00:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 13 /Volumes/Chimera
3/5/13 5:00:36.543 PM KernelEventAgent[45]: tid 00000000 received event(s) VQ_NOTRESP (1)
3/5/13 5:00:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Chimera
3/5/13 5:00:36.000 PM kernel[0]: AFP_VFS afpfs_DoReconnect: get the reconnect token
3/5/13 5:00:37.029 PM com.apple.backupd[48152]: Created new backup: 2013-03-05-170036
3/5/13 5:00:41.100 PM com.apple.backupd[48152]: Starting post-backup thinning
3/5/13 5:00:41.100 PM com.apple.backupd[48152]: No post-back up thinning needed: no expired backups exist
3/5/13 5:00:41.218 PM com.apple.backupd[48152]: Backup completed successfully.

The boot drive is failing, or you have some other hardware fault.
Back up all data immediately, then make a "Genius" appointment at an Apple Store to have the machine tested.
If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to bare metal from any of them.) Don’t erase the recovery partition, if present.
*An SSD doesn't need to be zeroed.

Time Machine "preparing backup" eternally upon wake from sleep

at a bit of a loss here...
iMac 24" (version which offered 7300GT as BTO option)
10.5.5 with all updates applied
LaCie 500 gig USB 2.0 drive directly attached.
Up until about two months ago, Time machine functioned fined. Then for some reason, the following started to happen. (no known reason, no software update related etc, that I know of)
scenario... Time Machine functions correctly EXCEPT when waking from sleep. If iMac wakes from sleep and attempts a backup immediately (e.g. more than one hour has passed), it gets stuck "preparing backup" forever. I've let it run overnight (actually as long as about 30 hours), it never stops. Finder and other programs become extremely non-responsive, machine is almost unusable. Literally, the only way out is to manually shut down external drive, with attendant warnings/errors.
What I've done:
1) deleted the time machine .plist file
2) erased, repartioned (as a single partition) external drive
3) started brand new time machine backup (takes about three hours)
At this point, time machine will backup up fine... I can force a successful backup, if I leave the machine running, at one hour it does a successful backup.
BUT, as soon as it goes to sleep, time machine is hosed.
The only workable method for using time machine is to turn the external drive and time machine off when not using it, and turn the whole shootin' match on to do what essentially becomes manual backups. These backup are fairly lengthy, as time machine also does lengthy "preparing backup", but they complete in about 30 minutes to one hour.
Given that time machine doesn't give mountable/cloneable backup, I'm probably going to go back to Carbon Copy Cloner. Still, I like the ease/regularity of Time Machine, and would use it if it works.
Any ideas?
thanks

It could be a number of things. There are lots of things that Time Machine does in order to "manage" backups -- apart from just copying data to the backup drive.
It has to manage the transition of hourly backups into daily backups and must also transition daily backups into weekly backups. Each time it does this it has to move a lot of data around. It also has to maintain indexes of everything so you can quickly find backups should you want to perform a restore.
I've also noticed that there are circumstances that can cause TM to question whether it can trust it's existing backup database... I've caught Time Machine saying that it needs to do a "deep traversal" of the backup (basically it wants to check and see what it really has) and this can take a very long time.
Still... 30 hours is an extremely long amount of time. I'm almost wondering if there's a problem with either your USB bus or your drive when they wake up such that you may be getting a huge number of retries on something that should have happened quickly.
I'd suggest you start the "Console" utility, select "All Messages" at the left, and then watch the messages being written to your log file. Not only does Time Machine log all of it's progress messages to the system.log (in more detail than you'd see in the Time Machine UI), but so do lots of other system processes. If you're getting USB bus problems the error messages would likely show up in the same log. I'm especially suspicious about non-TM related causes since you said you've already blown away your TM backups & preferences and started from scratch and you're still getting the problem.
Try re-creating your problem with the Console log messages being displayed and see if you can't see something in the log that would let you get a little closer to the root cause.
Regards,
Tim

Time Machine hourly backup seems a tad large

Hi all
Occasionally, my hourly Time Machine incremental backups to my Time Capsule seem a tad large. One hour the backup is a sensible size, then an hour later, when I've been doing very little on my machine, the backup is massive (as in, several gigabytes).
Not only that, but the backup seems to grow in size as its happening. the pictures below should help illustrate.
The backup is listed as being 719MB, only an hour after a more modest backup. Time Machine seems to be claiming that is has transferred all of the required backup:
!http://img6.imageshack.us/img6/4988/picture2gih.png!
But then, only two minutes later, see how the situation has changed:
!http://img5.imageshack.us/img5/3739/picture3m.png!
And the situation continues:
!http://img87.imageshack.us/img87/9339/picture5.png!
Any ideas? This issue happens intermittently (although it is happening now... that last image was taken a few minutes ago and the backup was still going - up to 3.1GB - before I told it to stop).
I'm not certain if Time Machine is actually transferring this amount of data to the Time Capsule or not.
Cheers.

Hi,
I had the same problem today as well. The last backup was done this morning at 2 a.m. When I turned my PowerBook G4 on again this afternoon, the backup size continually grew, just like on your machine, Rob. I aborted the backup a couple of times, deleted the inProgress file, but it always got bigger and bigger. After downloading Time Machine Buddy and Time Tracker, I just let Time Machnine "do it's thing". Luckily, I had enough free space on my WD MyBook 500 GB I use for the backups, because it stopped only at 24.8 GBs, after initially displaying 61,3 MB in the menu bar, and requesting 1.05 GB according to Time Machine Buddy.
Time Machine Buddy protocol:
Starting standard backup
Backing up to: /Volumes/My Book/Backups.backupdb
No pre-backup thinning needed: 1.05 GB requested (including padding), 32.74 GB available
Copied 139261 files (24.8 GB) from volume Macintosh HD.
No pre-backup thinning needed: 1.16 GB requested (including padding), 7.36 GB available
Copied 7042 files (2.0 MB) from volume Macintosh HD.
Starting post-backup thinning
Deleted backup /Volumes/My Book/Backups.backupdb/Claas Olthoffs PowerBook/2009-03-05-202501: 7.36 GB now available
Deleted backup /Volumes/My Book/Backups.backupdb/Claas Olthoffs PowerBook/2009-03-05-192342: 7.37 GB now available
Deleted backup /Volumes/My Book/Backups.backupdb/Claas Olthoffs PowerBook/2009-03-05-123736: 7.37 GB now available
Deleted backup /Volumes/My Book/Backups.backupdb/Claas Olthoffs PowerBook/2009-03-05-113526: 7.38 GB now available
Post-back up thinning complete: 4 expired backups removed
Backup completed successfully.
So I took a look at Time Tracker to see what was backed up. I was suprised to see, that the biggest chunk was my Macintosh HD/Library/Application Support folder. This folder is 23,9 GB in size, mainly because it contains Final Cut Studio media and templates. Time Machine backed it up completey. This seems weired, because none of the files I looked at in this folder were changed during the last couple of months, if not the last year, since I installed them. I don't know why Time Machine would backup all of those unchanged files.
For the sake of completeness, the external drives contains other, non-backup, files as well.
I hope this gives you some more information to work with Pondini.
Greetings,
Claas

Time Machine everytime backups everyting!

My main system disk "Macintosh HD", 500 GB
Media disk is exernal disk named "Media", 1000 GB.
My Time Machine disk is named "DeLorean" and its external 1,500 GB.
I have about 340 GB more free space in the Time Machine disk than my data currently uses up.
My problem is that the Time Machine VERY often starts its backup FROM THE SCRATCH!
Doing FULL BACKUP! Deleting over 800 GB of data. If you see my logs, you will see it doesnt like something about the external "Media" disk.
It does this thing called "Deep event scan at path:/Volumes/Media reason:must scan subdirs|"... * see logs later.
Funny thing is, if i delete/erase the backup, or let it do the FULL backup when it wants, it usually after that does the normal smaller backup just fine.
BUT if I unmount the Media disk even once and do one incremental backup(which it does fine), then after i mount the Media back, next time it does this FULL backup and says in the logs about the Deep even scan.
All my disks are encrypted via FileVault2. Shouldnt time machine still work or is this setup fine?
Here are the logs. Yesterday i even shuffled all my disks and erased the Media and the time machine disk and encrypted them again.
You can see the first full backup starting at 2 am, then ONE succesfull incremental backup while both disk were still mounted. When i woke up at (13:20 pm) I did one incremental backup without the Media (ummounted it) and then again new one with media mounted (13:29 pm) and BAM ! It started FULL backup (deleting 800+ GB of data). Nothing has been changed on the media disk during that time. Weird !
Logs showing fresh first new backup stuff:
Dec 18 01:03:48 imac com.apple.backupd[95130]: Copied 81.9 GB of 1047.6 GB, 1469 of 1156879 items
Dec 18 02:03:49 imac com.apple.backupd[95130]: Copied 172.8 GB of 1047.6 GB, 1516 of 1156879 items
Dec 18 03:03:50 imac com.apple.backupd[95130]: Copied 264.8 GB of 1047.6 GB, 1563 of 1156879 items
Dec 18 04:03:50 imac com.apple.backupd[95130]: Copied 357.1 GB of 1047.6 GB, 1615 of 1156879 items
Dec 18 05:03:51 imac com.apple.backupd[95130]: Copied 449.1 GB of 1047.6 GB, 1666 of 1156879 items
Dec 18 06:03:51 imac com.apple.backupd[95130]: Copied 541.5 GB of 1047.6 GB, 1696 of 1156879 items
Dec 18 07:03:52 imac com.apple.backupd[95130]: Copied 633.6 GB of 1047.6 GB, 1741 of 1156879 items
Dec 18 08:03:52 imac com.apple.backupd[95130]: Copied 725.6 GB of 1047.6 GB, 1786 of 1156879 items
Dec 18 08:10:55 imac com.apple.backupd[95130]: Copied 1796 files (736.3 GB) from volume Media.
Dec 18 09:03:53 imac com.apple.backupd[95130]: Copied 773.9 GB of 1047.6 GB, 621723 of 1156879 items
Dec 18 10:03:54 imac com.apple.backupd[95130]: Copied 803.6 GB of 1047.6 GB, 936589 of 1156879 items
Dec 18 11:03:54 imac com.apple.backupd[95130]: Copied 878.4 GB of 1047.6 GB, 1019840 of 1156879 items
Dec 18 12:03:54 imac com.apple.backupd[95130]: Copied 951.6 GB of 1047.6 GB, 1107382 of 1156879 items
Dec 18 13:03:54 imac com.apple.backupd[95130]: Copied 1034.6 GB of 1047.6 GB, 1110125 of 1156879 items
Dec 18 13:13:49 imac com.apple.backupd[95130]: Copied 1140722 files (1041.4 GB) from volume Macintosh HD.
Dec 18 13:13:58 imac com.apple.backupd[95130]: 1.72 GB required (including padding), 341.53 GB available
Dec 18 13:13:58 imac com.apple.backupd[95130]: Copied 6 files (0 bytes) from volume Media.
Dec 18 13:14:15 imac com.apple.backupd[95130]: Copied 6665 files (1.7 MB) from volume Macintosh HD.
Dec 18 13:14:17 imac com.apple.backupd[95130]: Copying Lion Recovery set
Dec 18 13:14:42 imac com.apple.backupd[95130]: Backed up Lion Recovery to /Volumes/DeLorean/Backups.backupdb
Dec 18 13:14:45 imac com.apple.backupd[95130]: Starting post-backup thinning
Dec 18 13:14:45 imac com.apple.backupd[95130]: No post-back up thinning needed: no expired backups exist
Dec 18 13:14:45 imac com.apple.backupd[95130]: Backup completed successfully.
Ends.
This backup i Initiated after i woke up, with both system disk and external "media" mounted:
Dec 18 13:22:02 imac com.apple.backupd[5781]: Starting standard backup
Dec 18 13:22:02 imac com.apple.backupd[5781]: Backing up to: /Volumes/DeLorean/Backups.backupdb
Dec 18 13:22:05 imac com.apple.backupd[5781]: 1.70 GB required (including padding), 340.96 GB available
Dec 18 13:22:05 imac com.apple.backupd[5781]: Waiting for index to be ready (100)
Dec 18 13:23:05 imac com.apple.backupd[5781]: Waiting for index to be ready (100)
Dec 18 13:23:48 imac com.apple.backupd[5781]: Copied 6 files (0 bytes) from volume Media.
Dec 18 13:23:55 imac com.apple.backupd[5781]: Copied 1780 files (8.6 MB) from volume Macintosh HD.
Dec 18 13:23:56 imac com.apple.backupd[5781]: 1.37 GB required (including padding), 341.39 GB available
Dec 18 13:23:56 imac com.apple.backupd[5781]: Copied 6 files (0 bytes) from volume Media.
Dec 18 13:23:59 imac com.apple.backupd[5781]: Copied 1596 files (268 bytes) from volume Macintosh HD.
Dec 18 13:24:00 imac com.apple.backupd[5781]: Starting post-backup thinning
Dec 18 13:24:00 imac com.apple.backupd[5781]: No post-back up thinning needed: no expired backups exist
Dec 18 13:24:00 imac com.apple.backupd[5781]: Backup completed successfully.
Ends.. This seems to work like it should.
Now, see the time stamps, i just toke some coffee and came back....
This next backup is done while "Media" drive has been umounted:
Dec 18 13:28:00 imac com.apple.backupd[5962]: Starting standard backup
Dec 18 13:28:00 imac com.apple.backupd[5962]: Backing up to: /Volumes/DeLorean/Backups.backupdb
Dec 18 13:28:01 imac com.apple.backupd[5962]: 1.37 GB required (including padding), 341.39 GB available
Dec 18 13:28:04 imac com.apple.backupd[5962]: Copied 1455 files (78 KB) from volume Macintosh HD.
Dec 18 13:28:04 imac com.apple.backupd[5962]: 1.37 GB required (including padding), 341.39 GB available
Dec 18 13:28:05 imac com.apple.backupd[5962]: Copied 115 files (93 bytes) from volume Macintosh HD.
Dec 18 13:28:05 imac com.apple.backupd[5962]: Starting post-backup thinning
Dec 18 13:28:05 imac com.apple.backupd[5962]: No post-back up thinning needed: no expired backups exist
Dec 18 13:28:05 imac com.apple.backupd[5962]: Backup completed successfully.
Incremental backup seems to finnish ok, without the "Media" drive.
This backup is the third one done just after couple minutes after i mounted the "Media" drive back on:
Dec 18 13:31:49 imac com.apple.backupd[6025]: Starting standard backup
Dec 18 13:31:49 imac com.apple.backupd[6025]: Backing up to: /Volumes/DeLorean/Backups.backupdb
Dec 18 13:31:49 imac com.apple.backupd[6025]: Deep event scan at path:/Volumes/Media reason:must scan subdirs|
Dec 18 13:31:49 imac com.apple.backupd[6025]: Finished scan
Dec 18 13:31:51 imac com.apple.backupd[6025]: 884.92 GB required (including padding), 341.39 GB available
Dec 18 13:31:51 imac com.apple.backupd[6025]: No expired backups exist - deleting oldest backups to make room
Dec 18 13:31:52 imac com.apple.backupd[6025]: Deleted backup /Volumes/DeLorean/Backups.backupdb/imac/2011-12-18-131415 containing 8.7 MB; 341.40 GB now available, 884.92 GB required
Dec 18 13:31:52 imac com.apple.backupd[6025]: Removed 1 expired backups so far, more space is needed - deleting oldest backups to make room
Dec 18 13:32:02 imac com.apple.backupd[6025]: Deleted backup /Volumes/DeLorean/Backups.backupdb/imac/2011-12-18-132359 containing 736.30 GB; 1.05 TB now available, 884.92 GB required
Dec 18 13:32:02 imac com.apple.backupd[6025]: Deleted 2 backups containing 736.31 GB total; 1.05 TB now available, 884.92 GB required
Dec 18 13:32:02 imac com.apple.backupd[6025]: Backup date range was shortened: oldest backup is now Dec 18, 2011
Dec 18 13:35:02 imac com.apple.backupd[6025]: Copied 526 files (4.3 GB) from volume Media.
Dec 18 13:35:03 imac com.apple.backupd[6025]: Backup canceled.
I canceled that scan(it would take about 12 hours again
OK. Couple questions:
- Why time machine does this deep scan? What does it actually mean?
- Why time machine thinks that it needs to do a 800GB worth of new backup. Those data have not changed a bit (they are movies).
- How its related to the unmount/mounting the Media drive?
I would really hope some answers from somebody. I have strugled with this issue almost a month now.
Thanks!

ECONOMAN wrote:
Time Machine Incremental Backups S...L...O...W and seem to bog down things so as to make the machine unusable. Why doesn't it simply backup changes, not the entire drive (less exclusions)?
Normally, that's exactly what it does. So start by calming down.
And, it gobbles processing power so I can't even check mail.
Can you schedule the frigging thing or do I just stop it all the time in order to get anything done?
It's cute, but kind of worthless.
First, are these backups larger than you think they ought to be? If so, that's likely at least part of your problem. See #D4 of the Time Machine - Troubleshooting *User Tip,* also at the top of this forum, for some possible causes and a way to find out just what's going on.
If that's no help, or they're still slow, try all the things in #D2 of the Troubleshooting Tip.
If that doesn't help, post back with details, including all the messages, your setup (especially the destination for the backups), what you've done, and the results.

Time Machine error: backup disk image could not be created

Iet up my new time capsule day and it's working great. Now that I've got everything sorted out, I'm ready to do the initial time machine back up on it. I went into preferences, changed the backup location to my TC and clicked 'back up now'. Very quickly I get a message that the backup failed: "Time Machine Error - The backup disk image could not be created".
I've searched the apple support area but haven't been able to figure this one out. Can anyone help, please? This is an initial backup. (FYI, it worked great on my old external drive.)
Many thanks

I had the same problem. I installed my Time Capsule, fired up Time Machine and got an error that said "The backup is too large for the backup volume. The backup requires 436.8 GB but only 182.2GB are available."
Coincidently, these are the same sizes as the space used and the space available on my iMac's drive.
I looked in /Volumes and saw that the sparsebundle was being created on the local disk and not on the main disk. Trying to backup again gave me the "Time Machine error: backup disk image could not be created." message.
I poked around the forums, and found a post about the machine name setting in sharing. I decided to give it a look, and lo and behold, I did not have a machine name. So I gave my box a name, kicked off Time Machine again, and it worked.

HT3275 Time Machine Indexing Backup has been taking an extremely long time following a Single User launch. How can I fix this?

My MacBook Pro has not been launching properly and in addition has suddenly gone to a blue or white screen countless times. I am preparing to take it to the apple store but first I need to back it up as I have not done so since two weeks ago. In order to make it start properly, I launched the computer in Single User Mode, then ran time machine. It has been about 15 hours and time machine still says that it is indexing the backup. How can this be fixed? Surely it shouldn't take this long. Thanks in advance.

Hi jonathanfromjericho,
If you are having an extended index period during a Time Machine backup, you may find the following article helpful:
AirPort Time Capsule: Initial backup is interrupted
http://support.apple.com/kb/HT1176
Regards,
- Brenden

FYI: No Sleep during Time Machine initial backup

Similar Messages

Maybe you are looking for