Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

time machine hangs after Lion installed

It's taking an enormous amount of time to update. Thought at first it was normal with the first backup when there was like 16gb to do, but each subsequent back up is still slow despite less amount of memory. it seems to hang up on either "Preparing for backup" or "Indexing backup"


Time Machine buddy:

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

etc


On console:

7/20/11 10:10:23.000 PM kernel: IOSurface: buffer allocation size is zero

7/20/11 10:10:50.000 PM kernel: IOSurface: buffer allocation size is zero

7/20/11 10:12:20.000 PM kernel: IOSurface: buffer allocation size is zero

7/20/11 10:12:30.000 PM kernel: IOSurface: buffer allocation size is zero

7/20/11 10:12:44.000 PM kernel: IOSurface: buffer allocation size is zero

7/20/11 10:13:02.000 PM kernel: IOSurface: buffer allocation size is zero

MacBook, MacBook Pro, iMac, iPhone 3g, Mac OS X (10.6.1)

Posted on Jul 20, 2011 10:41 PM

Reply
42 replies

Jul 24, 2011 4:07 PM in response to Pondini

Thanks.


The last seemingly (according to the Time machine pref pane) completed backup looks like this:

Starting standard backup

Attempting to mount network destination URL: afp://Glenn%20Gukild@Glenn-Gukilds-Time-Capsule.local/Data

Mounted network destination at mountpoint: /Volumes/Data using URL: afp://Glenn%20Gukild@Glenn-Gukilds-Time-Capsule.local/Data

QUICKCHECK ONLY; FILESYSTEM CLEAN

Disk image /Volumes/Data/Glenn Gukilds MacBook.sparsebundle mounted at: /Volumes/Time Machine-sikkerhetskopier

Backing up to: /Volumes/Time Machine-sikkerhetskopier/Backups.backupdb

1.38 GB required (including padding), 51.52 GB available

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready





According to the widget however "Status of backup unknown - check log messages"


The widget actually gives the last succesful backup as one completed earlier today.(Finishing in 15hours, 57minutes, 27seconds!)

After a looong list of "Waiting for index to be ready (100)", the last entries are as follows:



Waiting for index to be ready (100)

Waiting for index to be ready (100)

Waiting for index to be ready (100)

Copied 0 bytes of 32.9 GB, 0 of 324101 items

Copied 465.0 MB of 32.9 GB, 217546 of 324101 items

Copied 2.9 GB of 32.9 GB, 291318 of 324101 items

Copied 8.6 GB of 32.9 GB, 291318 of 324101 items

Copied 11.8 GB of 32.9 GB, 291318 of 324101 items

Copied 17.2 GB of 32.9 GB, 291318 of 324101 items

Copied 23.8 GB of 32.9 GB, 291318 of 324101 items

Copied 26.8 GB of 32.9 GB, 335338 of 335338 items

Copied 366779 files (27.9 GB) from volume Macintosh HD.

1.67 GB required (including padding), 51.58 GB available

Copied 7894 files (59.2 MB) from volume Macintosh HD.

Starting post-backup thinning

Deleted /Volumes/Time Machine-sikkerhetskopier/Backups.backupdb/Glenn Gukilds MacBook/2011-06-23-001955 (142.8 MB)

Post-back up thinning complete: 1 expired backups removed

Backup completed successfully.

Ejected Time Machine disk image.

Ejected Time Machine network volume.


The current backup looks identical to the first one listed, after about 30minutes, it starts its "waiting for index to be ready (100)" cycle, repeating about once pr. minute.


Jul 24, 2011 7:11 PM in response to Pondini

I've been waiting fro 20 min and all I get is "waiting for index to be ready"


This is after I junked my previous Time Machine bundle, reformated, and started fresh. However, I think there was a network interuption (doing this via Airport Extreme) with the initial load (after almost 24 hours) and the backup process restarted. However I'm stuck in "waiting for index to be ready" purgatory.


How do you fix a corrupt index?

Jul 26, 2011 9:57 AM in response to gaffield1997

I finally got Time Machine to restore all my user files, settings, etc. The issue was an extra folder that was in my backups - the folder contained two corrupt files that TM kept backing up. Once I deleted the folder from the Time Machine hard drive, it worked perfectly.


So, for anyone that is finding TM just won't quite finish the restore (hanging with one minute to go), look inside your backed-up files for an "extra" folder. Delete it and try again.


Cheers,


Dave

Jul 28, 2011 3:45 AM in response to gaffield1997

the "kernel: IOSurface: buffer allocation size is zero" don't have anything todo with Time Machine, since lots of people seem to have that issue lately (and it seems to be adobe flash related). As for the issue with time machine, i had to repair my keychain first before mac osx lion would work "normal" at all

see the discussion here: https://discussions.apple.com/thread/2324567


also, you can try if installing flash player 64-bit 11.0 resolves your issues: http://bit.ly/pNtLWS

Mar 13, 2012 2:44 PM in response to gaffield1997

Don't know if this is the right thread to comment on, but here goes...


I upgraded to Lion on my Mac Pro Xeon and my MacBook Pro at the same time. The desktop mac works just fine after the upgrade, and TimeMachine backs up to the Time Capsule just fine.


The MBP won't backup. It wanted to do a full backup but couldn't do so because the TC was full of the last backup (Leopard), and after upgrading Lion wanted to do a full backup. Five days in, I've tried changing the backup drive to a USB drive connected directly. That attempt to backup just failed several times, so after using Terminal to delete the spans in the old sparsebundle to clear room, and telling Time Machine to not back up any system files to save space, I've been trying to go back to the Time Capsule. Still no luck. The computer slows down to unusability, and after 6 hours today it has successfully backed up 4Gb. Estimated time to completion, 16 days.


I'm now using Migration Assistant to move the user files and applications, etc. to a 2Tb USB drive that has Lion installed on it, and then plan to wipe the main HD in the MacBook Pro. Then reinstall Lion and reverse migrate the stuff back.


Should I have to do all this crap? I've really looked around on the support groups and although others have had similar problems, none of the solutions I've read have had any effect. Without a backup in place I'm very nervous. If anyone has anything to offer that might help other than what I'm doing, I'd sure appreciate it.

Mar 13, 2012 3:30 PM in response to neilpet

neilpet wrote:


Don't know if this is the right thread to comment on, but here goes...

No, it isn't. You're not having the same problem.


I upgraded to Lion on my Mac Pro Xeon and my MacBook Pro at the same time. The desktop mac works just fine after the upgrade, and TimeMachine backs up to the Time Capsule just fine.


The MBP won't backup. It wanted to do a full backup but couldn't do so because the TC was full of the last backup (Leopard), and after upgrading Lion wanted to do a full backup.

Surely you mean Snow Leopard? How did you do the upgrade -- did you just install Lion over Snow Leopard, or did you do a "clean install"? If a clean install, how did you put your data back?


Five days in, I've tried changing the backup drive to a USB drive connected directly. That attempt to backup just failed several times,

Why? With what message? What happened?


so after using Terminal to delete the spans in the old sparsebundle to clear room,

What? What "spans" are you talking about? What, exactly, did you do?


and telling Time Machine to not back up any system files to save space, I've been trying to go back to the Time Capsule. Still no luck. The computer slows down to unusability, and after 6 hours today it has successfully backed up 4Gb. Estimated time to completion, 16 days.

Without knowing what you did to the sparse bundle, it's impossible to tell. Have you tried repairing the backups, per #A5 in Time Machine - Troubleshooting?

Mar 13, 2012 7:48 PM in response to gaffield1997

sigh...


re: What exactly did I do? I deleted the sparsebundle, retrieving the space that it was occupying on the Time Capsule. Never mind my mispeaking re: the spans. The sparsebundle was deleted.


I attempted to repair the sparsebundle that was related to the MBP, then deleted it. I've run disk utility on every drive remotely associated with the MBP, and all pass the tests. Nonetheless, my laptop is non-functional at this point.


I'll stop this commentary, as it is becoming clear to me that the problem is more likely with corrupted files in my user directory. I'll salvage what I can and go forward.

Mar 13, 2012 7:54 PM in response to neilpet

neilpet wrote:

. . .

re: What exactly did I do? I deleted the sparsebundle, retrieving the space that it was occupying on the Time Capsule. Never mind my mispeaking re: the spans. The sparsebundle was deleted.

Ah, ok, I was afraid you'd deleted parts of it or something.


I'll stop this commentary, as it is becoming clear to me that the problem is more likely with corrupted files in my user directory.

Could be, but Disk Utility should have caught that.


Have you tried the Intel-based Macs: Using Apple Hardware Test? If not, run the Extended tests (that may take an hour or more, depending on how much RAM you have). Write down any error code(s) it shows.

time machine hangs after Lion installed

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.