Time Machine restore stuck at 99%

I'm restoring my system from a TM backup and it's been running over night, near 11 hours at this point. Last night it spent hours at about 6% and I left it. When I woke up I was happy to see that it made it to 99.5 percent but when I moved the lightly, the spinner wheel popped up.
Right now it's been on the 99.5%, the blue level is not pulsing, and the spinner wheel is spinning. However, I can still hear the drive working in the same manner that it has been.
Any suggestions? Should I just let it sit for even longer and hope that it works itself past this or do you think it's frozen?
Message was edited by: skottie

skottie wrote:
I'm restoring my system from a TM backup and it's been running over night, near 11 hours at this point. Last night it spent hours at about 6% and I left it. When I woke up I was happy to see that it made it to 99.5 percent but when I moved the lightly, the spinner wheel popped up.
Right now it's been on the 99.5%, the blue level is not pulsing, and the spinner wheel is spinning. However, I can still hear the drive working in the same manner that it has been.
Any suggestions? Should I just let it sit for even longer and hope that it works itself past this or do you think it's frozen?
Hi, and welcome to the forums. Sorry about it being under such circumstances.
Where are your backups? If this is being done wirelessly, and you have a fairly large system, 11 hours may not be too long. Do you remember how long your very first backup took? If so, adjusting for how much data you've added since then, a full restore should take somewhat less time, other things being equal.
If it's been stuck at 99.5 % for a very long time, it may be hung, or (as happened to me once), it may actually be done but isn't saying so! About all you can do is force power-off and reboot.
If it wasn't done and doesn't reboot, start over. Disconnect everything but your keyboard and mouse (and external drive, if that's where your backups are). If you're using a Time Capsule or Airport, connect via an Ethernet cable. Make sure all connections are tight. If it's an external drive, try another cable and port, if you can. When you re-start the process, monitor the installation by selecting Window, then +Show Log+ and +Show All logs+ from the menubar. That should give you a better idea of what's going on; if it stalls again, at least you'll know where it was.
If all else fails, you may have to reinstall OSX and "migrate" from your TM backups. See the *Erase, Install, & Migrate* section of the Glenn Carter - Restoring Your Entire System / Time Machine *User Tip* at the top of this forum

Similar Messages

Time machine restore stuck on filevault password screen

I have a new macbook pro. I am trying to restore from a backup on timemachine through migration assistant. The problem is that the backup is too big to fit on this new computer's storage, so it attempts to do it and then fails. which is fine, because it asks me which folders I want restored. When I select the only folder I want restored It then becomes stuck at the filevault password screen. (see attached image).

The warranty entitles you to complimentary phone support for the first 90 days of ownership.

Can't Boot After New HD + Time Machine Restore

So a couple days ago my 27" iMac running Snow Leopard started making some weird noises and stalling out. Annoyed, I talked for a couple hours with apple tech support which eventually lead me to run an Apple Hardware Test. This test returned the error
"Alert! Apple Hardware Test has detected an error.
4HDD/11/40000000 SATA(0,0)"
I scheduled an appointment at the Genius Bar, and they replaced the hard drive.
After that I got it home and did a System restore from my time machine backup. It finished fine, but when I restarted it got stuck on the grey apple screen with the spinning dial thing.
I called apple back and they had me do a couple things like repair disk, verify disk, and one person had me reboot into this command line mode and type some stuff in. Nothing worked. After that They had me try to reinstall the OS first from archive, and next by erasing the hard drive and doing it. Both times the install fails with a big yellow exclamation point saying that it couldn't install support files and the OS couldn't be installed.
Any ideas how to fix this?
I'm currently trying to restore from my time machine backup again, but I'm not hopeful.

Here's what I got - apologies for any formatting peculiarities.
The problem: 10.6.6 mac won't boot after time machine restore to disk.
Further symptoms: Booting with Command-v shows several errors: usually blued and loginwindow collapse with errors from launchd. Errors will be of the style "dyld: Symbol not found: CSSMOID_APPLE_TP_MACAPPSTORERECEIPT" and other CommerceKit / CommerceCore framework errors.
A solution: Your Framework Security library may be an older version (possible cause with Time Machine below). The easiest way to fix this is to find another, working 10.6.6 Mac, and update the Security library on the broken machine.
Identifying if you're affected:
1) Boot the broken machine into "target" mode - hold "Command-t" during boot until the [Firewire|http://itunesu.utah.edu/terms/images/Firewire_Icon.png] icon appears.
2) Connect the broken machine to the working 10.6.6 machine with a firewire cable.
3) On the working machine, the disk of the broken machine should mount.
4) Open Terminal
5) Run "ls /Volumes" - the name of disk you mounted should be there (in this example, we'll use "Macintosh HD".)
6) Typing in the path of the broken machine, run:
<pre>
nm /Volumes/Macintosh HD/System/Library/Frameworks/Security.framework/Versions/A/Security | grep random_fd | cut -d. -f2
</pre>
(this does a dump of the library, looking for the version value)
If this comes back with the value 22457 (or less?), your Mac is not booting because it does not have the updated version of the Security library, which is required in 10.6.6 since Snow Leopard added the Appstore / Commerce framework.
Fixing if you're affected:
1) First, make sure the working 10.6.6 Mac has a correct version of the framework:
<pre>
nm /System/Library/Frameworks/Security.framework/Versions/A/Security | grep random_fd | cut -d. -f2
</pre>
For 10.6.6, this should be at least "22458"
2) *Be extremely careful at this point* - Make sure on the mounted disk (not the machine you are working on!) run the following
<pre></pre>
2a) Make a backup of the broken library
<pre>
mkdir /Volumes/Macintosh HD/savedLibrary
cp /Volumes/Macintosh HD/System/Library/Frameworks/Security.framework/Versions/A/Security /Volumes/Macintosh HD/savedLibrary
</pre>
2b) Copy the working version over the non-working version:
<pre>
cp /System/Library/Frameworks/Security.framework/Versions/A/Security /Volumes/Macintosh HD/System/Library/Frameworks/Security.framework/Versions/A/Security
</pre>
3) Eject the mounted disk from the working Mac, disconnect the firewire cable, and reboot the "broken" Mac. It should come up.
If it doesn't, you have problem(s) that are probably outside the scope of this. I'd also suggest restoring your original security library that you saved off.
Suspected cause:
It appears that Time Machine never recorded the change to the Security library after the update. If the library hadn't changed, the machine should have failed to boot like it did after restore the moment a 10.6.6 update was applied.
Inspecting the contents of my Time Machine backups before and after updating shows that Time Machine never updated the Security Framework library - why is still not 100% determined, but restoring from it is definitely broken. Combing through the backup databases on my Time Machine disk:
(I upgraded to 10.6.6 on January 6)
<pre>
for name in 2010-12-30-093337 2011*
do
echo -n "In backup on ${name}, version of Security library is: "
nm "${name}/Macintosh HD/System/Library/Frameworks/Security.framework/Versions/A/Security" | grep random_fd | cut -d. -f2
done
</pre>
In backup on 2010-12-30-093337, version of Security library is: 22457
In backup on 2011-01-04-100707, version of Security library is: 22457
In backup on 2011-01-05-082402, version of Security library is: 22457
In backup on 2011-01-06-092846, version of Security library is: 22457
In backup on 2011-01-07-094827, version of Security library is: 22457
In backup on 2011-01-10-093559, version of Security library is: 22457
In backup on 2011-01-11-110542, version of Security library is: 22457
In backup on 2011-01-12-094137, version of Security library is: 22457
In backup on 2011-01-13-103238, version of Security library is: 22457
In backup on 2011-01-14-113145, version of Security library is: 22457
In backup on 2011-01-18-112856, version of Security library is: 22457
In backup on 2011-01-20-114953, version of Security library is: 22457
In backup on 2011-01-21-103642, version of Security library is: 22457
In backup on 2011-01-24-102321, version of Security library is: 22457
In backup on 2011-01-27-002508, version of Security library is: 22457
In backup on 2011-01-27-011931, version of Security library is: 22457
In backup on 2011-01-27-104406, version of Security library is: 22457
In backup on 2011-01-27-114322, version of Security library is: 22457
In backup on 2011-01-27-123928, version of Security library is: 22457
In backup on 2011-01-27-134523, version of Security library is: 22457

Time Machine Restore Mangles Permissions and Groups

Circumstance:
My Macbook Pro running 10.5.5 gave a gray spinner after a restart last week. The restart was to clear out a couple of system processes eating up CPU when I had left it alone for a few hours.
Action:
After Disk Utility, zapping PRAM, and the probably some other standard trouble-shooting actions didn't fix the stuck start-up problem, I decided to try a full system restore from my Time Machine backups. I had previously successfully restored individual folders and files. Time Machine backs up wireless to a USB hard drive connected to my AirPort Extreme. To speed up the restore, I ran an Ethernet cable to the MBP from the Airport. The restore completed successfully. All the folders & files are correct, looks the same, etc. I restarted using the restored boot drive.
Problem:
The MBP is like a museum now--I can look but I can't touch. I first noticed something was wrong after logging in the first time because I couldn't move a file into a folder via drag-n-drop. Then Terminal went into a spinning beach ball when I opened it. Spotlight was not running. Then I noticed that my entire boot disk was read-only. I got info on the boot disk, and the Users & Groups list was strange--everyone was read-only, "wheel" had read-write and was the owner, and staff had read-write. Basically, it's like me, the Finder, an all applications have lost all their write/execute permissions on the entire drive.
*Unsuccessful Steps Taken:*
Ran Disk Utilities' Repair Permissions from Leopard dvd. Ran fsck -fy after mount / -uw from Leopard dvd Terminal and from single-user boot mode. Time Machine restore direct from TM disk via USB. Joined my user to wheel group. Changed my user password from Leopard dvd (which repairs home folder permissions). Played with chown to make all wheel-owned items staff-owned.
*Open Theories:*
Airport Time Machine restores strips ACLs and Permissions. I have to restore over wireless, not ethernet or usb. My TM backup is screwed up somehow.
Whew. This has been going on for a while, so I'm ready to give up and do an Archive & Install and begin manual migration from the backups, but my MPB is a fine-tuned machine and I hate to lose that, especially since it taunts me by being so close to normal (I can see everything! My desktop background and apps are there!).
Any help much appreciated!

The "full restore" from Time Machine is only for OSX drives.
For data-only drives, use the Time Machine browser (the "Star Wars" display). See Time Machine - Frequently Asked Question #15.
Depending on your setup, you may also want to review Transferring Home Folders not on a Startup volume.

Computer wont boot after time machine restore

Hi Guys,
I did a time machine restore last night and after it completed and i did a restart the computer gets stuck on the gray screen. I waited like 2 hours and it still doesn't get past that screen. I have tried every boot shortcut including target mode, single user mode etc. One problem is that i have disabled sounds so i cant hear the chime therefore not knowing when to push and hold the "t" or "c" button.
Am i doing something wrong? when do i start holding c or t?
Even when i put the mac osx dvd in it won't even boot from that. also tried holding c and booting from the dvd and that doesn't work.
please help

Begin with the usual diagnostics in hopes of successfully booting your macbook. As Eric mentioned, have you tried booting with the Option key ?
If that fails, try the following, before forced to a re-install of the OS:
1: Boot up the machine via Safe Boot by holding the shift key. Since your volume is off, ideally you want to wait a second or two where the chime would come in. Note that if the safe boot is successful it will take some more time to boot as it checks for disk errors. Make sure and repair your permissions if you get through !
2: If that fails reset your PRAM, http://support.apple.com/kb/HT1379

Time Machine restore fail - best method to reinstall OS?

I've just had a Time Machine restore fail on me, startup gets to blue screen but no further. Also tried the next previous backup. Trying to decide whether to reinstall Snow Leopard on my not-quite-restored drive and then do the combo update to the last OS version, or whether to do a clean install (wipe drive) and then use the Migration Assistant to import everything.
I have a ton of software / plugins authorised which will take me an age to reinstall, hoping that whichever method will retain all the pref files in macintosh hd/library and user/library. That being said I was in the process of trying to fix my intermittent system freezes, it was happening at the last TM backup so maybe aiming to return to duplicate system / user folders is a bad idea?
Many thanks for any help.
Harry

hazza26 wrote:
Hi again
I have ended up having to erase my drive and do a fresh install of SL. When I get to the welcome page I opt to import all my setting from my TM backup. It started ok this morning but the progress bar has been stuck at "4 hours 46 mins left" for the whole day. How best to proceed now?
Cancel it. You'll probably have to turn your Mac off via the power button.
Can I do a disk repair on the backup data, and if so how?
Yup. See #A5 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum). Then you'll have to erase your OSX volume and install OSX again, since the transfer was incomplete.
Or, if the repair finds and fixes problems, you might want to try a full restore again (much less likely to have problems with transferred apps), but perhaps from an earlier backup, before the problems started. If that seems to complete normally, but won't boot, then just install a fresh version of OSX over the old one, then download and install the "combo" update and repair permissions.
Or should I try to mount the backup and manually pull off all my critical data?
Only as a last resort. You may have all sorts of permissions problems that way, and of course will have to reinstall all your 3rd-party apps.
Thanks again for your much appreciated support
You're quite welcome. Hang in there!

Mail problem after Time Machine restore

New to the community..........hello everyone!
I just did a Time Machine restore and everything seems to be fine except
for the fact that my mail seems to be stuck.........spinning as if there was mail to be sent out?
I found a post with a similar problem: http://discussions.apple.com/thread.jspa?threadID=1897021&tstart=0
Just wondering if I should follow the advice mentioned on that post or is there an easier way to resolve this issue?
Thanks

Make sure your out going mail server set up is correct according to what your ISP requires. Mail>Preferences>Accounts>Account Information.

What to do when time machine seems stuck on "Preparing Backup"

This issue is happenning on my macbook pro, mid 2010. My drive setup is that I have a partition which I dedicated to time machine backups. The total size of my drive is 500GB, and I partitioned about 100GB for time machine. The reason for that is I only needed a few space since I setup time machine to include only the system and the apps, and NONE of the libraries such as itunes or photos. This means that the only backup will be for the system, profiles, and the app. I have been running this for a few months andhas been doing OK until up to now.
My problem is that my time machine seems to get stuck on "Preparing Backup". The latest backup was done last Nov 8, 2011, whcih is about 11 days from now. I am also aware that the time machine drive has only about 200 mb space left, but I am not worried at all because I've always TM to delete the oldest backup to free up space. My oldest backup was still Sept 8, and I'm ok if that will be deleted.
So I'd like to find out why it still stuck on "Preparing backup" ,and I am wondering if deleting a backup can solve it. Can it? what do I do to solve this?
Also, I use my computer alot , so it is basically running for about 18 hours a day, but still time machine didn't quite work well. I have tried reparing the disk using disk utility, but that didn't help.

Comments inline below.
Pondini wrote:
joshua raphael wrote:
This issue is happenning on my macbook pro, mid 2010. My drive setup is that I have a partition which I dedicated to time machine backups. The total size of my drive is 500GB, and I partitioned about 100GB for time machine. The reason for that is I only needed a few space since I setup time machine to include only the system and the apps, and NONE of the libraries such as itunes or photos.
You may want to revisit that strategy:
A backup on the same drive isn't very secure -- when (not if) the HD fails, you risk losing everything.
In most cases, if there's a problem with OSX the best way to fix it is to just install a fresh version. But you can't do that from that backup.
Indeed!
Backing-up apps that way will also be useless in some cases. 3rd-party apps that came with their own installers put other files in other places (and sometimes "helper" apps as well). Unless you know what and where they all are, and restore them, too, the restored app won't work properly, if at all.
I think you're confusing each other with terminology. iTunes music and iPhoto pictures are NOT "Libraries", which has a specific meaning when it comes to OS X. "Libraries", in OS X normally refers to /Libraries and ~/Libraries folders. This is not where iTunes music and iPhoto pictures are stored. iTunes music and iPhoto pictures are stored within ~/Music and ~/Pictures, respectively.
I have tried reparing the disk using disk utility, but that didn't help.
Disk Utility changed a bit in Lion. When you select an entire disk, it only repairs the partition map, not all the volumes. You must repair each one separately.
Wow, good to know. (What a stupid change to make, for backwards compatibility, if for no other reason!)
See #D1 in Time Machine - Troubleshooting to figure out why the backups are hanging.
Whew. This editor makes it so hard to make comments inline. The key thing when time machine seems stuck is patience. Sometimes it needs to be left to run overnight. Unfortunately, it doesn't log or report it's progress very well.
Opening Time Machine settings in Preferences plus a command like this left running in Terminal.app is how I monitor progress. And even so, there is very little logging indicating progress.
sudo tail -f /Volumes/Time Machine/Backups.backupdb/My\ Computer/2012-07-11-133352.inProgress/.Backup.363731632.496216.log
The parts in italics will need to be adjusted. Tab completion makes this easy, e.g type
sudo tail -f /Volumes/
and hit tab, type the first few letters of the relevant volume name, hit tab...
Also, I have a hypothesis which needs testing.
I know that Time Machine gets confused if one deletes large files from a backup - specifically, Time Machine doesn't recognize that the size of the backup has changed.
I know because this made restoring a thinned out time machine backup ("thinned out" by deleting files from within the GUI while inside the Time Machine) to a small SSD harder than it should have been. I had to restore to a big disk and then clone that volume to the SSD - even though the SSD had enough space, Time Machine didn't think so; it didn't "understand" that it had been thinned.
My hypothesis is that Time Machine also gets confused if the Time Machine partition is resized. I shrunk a Time Machine partition (no it wasn't on my main disk!) and about that time, Time Machine stopped working. After thinning the volume, it started working again.

Update from 10.7.2 to 10.7.3 blown - Time Machine Restore blown

Hello,
summary of events:
Update form 10.7.02 to 10.7.3 went wrong
After Time Machine Restore no more Recovery Partion
Lost about what to do
On Saturday, I startet to update 10.7.2 to 10.7.3 on my MB Pro 15" (2007) Apples Software Update showed the combo update, and so I started download and installation. Just before that, I had run Time Machine on an external USB drive, so I was relaxed.
After about 2 hours, the update was still running with no progress. After another hour, I forced a restart. Not very suprisingly, after the login, the wheel beneath the Apple logo kept on running.
So I restarted from the Recovery Partition, selected my Time Machine-Backup from the external USB drive, selected my internal HD as target and clicked on "go".
While the progress bar showed progress, I waited. Then it seemed to be complete and the MBP restarted. Now I got a folder with a question mark. My heart rate did not yet accelerate, since I had a back up, right?
So I restarted again trying to boot from Recovery Partition - BUT, there was no longer a Recovery Partition. Or at least, nothing I could boot from.
What options do I have? I could get my hands on a DVD that contains an Lion installation from the app store, but that is not the most recent version, as far as I can tell. If I would go that way:
Does the version of the Lion-app matter?
Will it create a Recovery Partition?
If not, how else could I restore a complete Time-Machine backup?
Any help and suggestions are very welcome :-)
Regards
Jimbo
Naturally, I a am mad as **** at Apple. First, that they abandoned physical media for Mac OS distribution, and secondly that some not so bright lad thought it not necessary to secure the availability of the Recovery Partition under any circumstances short of phyical damage. This really *****, guys!

Ok... I'm not sure if the following suggestions will work with Filevault 2 enabled. I guess you can try after you create a backup for safety.
You can recreate the Recovery HD two ways. One is to reinstall Lion using a bootable USB thumb drive of the Recovery HD created with the Lion Recovery Disk Assistant. Or from a bootable USB thumb drive with the Lion installer restored to it.
A second way, which I have used many times, is to follow the instuctions at this site using Terminal commands. Step 3 is what you want to follow. The instructions use the RecoveryHDUpdate.dmg file downloaded from Apple to recreate the Recovery HD. It works great!

How do I safely stop a Time Machine Restore midway through?

I started a Time Machine restore from backup at about 1pm this afternoon.
After about 15 minutes of estimating the size of the files to be transferred, it gave me a 19hr estimate for transfer time. I had heard that it could take awhile, so I wasn't totally blown away by the number.
I'm backing up about 200 GB. Well, I'm about 2 hours into it, and the time remaining has been fluctuating from 19+ hours to 14 hours. I'm at about 18 hours right now.
I'm beginning to question the ethernet cable I'm using to transfer the data, and wishing I used a USB 2.0. I've also read up on a bunch of other threads about how painfully slow Time Machine can be, and there seems to be little rhyme or reason as to when it's slow vs when it's somewhat reasonable.
So, I guess there are two questions.
Question 1) Can I safely power down, swap cables, and retry? What happens to the data that's already been pulled over?
Question 2) Should I just let it run for the next 18 hrs? I've also read other horror stories where people return to their machines after the time estimated, and it's hardly budged.
Any help would be AWESOME! If i could give you a billion help points, i would!

majmanMac wrote:
Was doing a full restore from scratch - I lost a hard drive on Monday, and just got a new one put in. Turns out the estimate was about right, as I'm now writing this from my restored machine.
Yay!
I was restoring from a Time Capsule. For some reason I just assumed it had a USB port.
Ah, yes, it does, but it's for connecting a printer or USB drive, not a Mac.
My concern that i would come back to it this morning and find it still updating has been put to rest. Phew!
Glad it's sorted out, but it does seem like there may be a problem -- that's awfully slow. See #D2 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum).
And be forewarned: since you have a new drive, Time Machine's next backup will almost certainly be a full one, so remain connected via Ethernet. If there isn't enough free space for that, it will take an extremely long time for Time Machine to delete a lot of old backups to make room. You might consider manually deleting a lot of them, per #12 in [Time Machine - Frequently Asked Questions|http://web.me.com/pondini/Time_Machine/FAQ.html] (or use the link in *User Tips* at the top of this forum).

Lots of permission errors after a full time machine restore.

So I replaced my hard drive in my MacBook Pro with a 500GB and when in reinstalled leopard i jest did a time machine restore, now if I check the permission i have this long list that it jest can not seam to fix. Here is the list. What should i do about it?
Reading permissions database.
Reading the permissions database can take several minutes.
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/DVD.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSettings.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSources.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Movies.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Music.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Photos.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Podcasts.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/TV.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/BackRow.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "Applications/iTunes.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "Applications/iTunes.app/Contents/Frameworks/InternetUtilities.bundle/Contents/ CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "Applications/iTunes.app/Contents/Resources/iTunesHelper.app/Contents/CodeResou rces", should be -rw-rw-r-- , they are lrw-rw-r-- .
Warning: SUID file "System/Library/Filesystems/AppleShare/afpLoad" has been modified and will not be repaired.
Warning: SUID file "usr/bin/setregion" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/Install.framework/Versions/A/Resources/runner " has been modified and will not be repaired.
Warning: SUID file "System/Library/Printers/IOMs/LPRIOM.plugin/Contents/MacOS/LPRIOMHelper" has been modified and will not be repaired.
Permissions differ on "System/Library/PrivateFrameworks/iLifeMediaBrowser.framework/Versions/A/CodeRe sources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/CodeResourc es", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/BlackAndWhiteEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/CubeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/DissolveTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/DropletTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/FadeThroughBlackTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/FlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/MosaicFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/MosaicFlipTransitionSmall.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/PageFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/PushTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/RevealTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/SepiaEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/TwirlTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/WipeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
ACL found but not expected on "Applications".
Permissions repair complete

This has been reported elsewhere in these forums.
They are not errors, they are warnings and informative statements, but not real errors and they can be ignored as you will find when you search
for the other posts about this exact same topic.
If you uncheck the Show Details" box in DU, you will only see real errors and these will not show up.
Yes they are annoying, and if you read my other post you get more information.

Can I use a Time Machine restore from an older OS to Mavericks?

I ask because I tried about 2 years ago and had no luck. Here's a little back-story so my situation isn't confusing...
My iMac (2010) has been having tons of issues lately. More specifically, when I attempted to upgrade to Mavericks last week, it came back with S.M.A.R.T. errors after a scan, so it wouldn't allow me to update. So, in preparation for the HDD to crap out on me, I did frequent back-ups using Time Machine. Well, the day finally came and my iMac won't "turn on" anymore. When I turn it on, it sits at the Mac loading screen for several minutes and then just goes to a blank white screen. (NOTE: This isn't part of my question but if anyone has any suggestions on fixing this, please let me know, thanks!)
So, back to my question. If I buy a new iMac or a new macbook or whatever, will it be possible to use my Time Machine back-ups to restore everything on it or will it not allow me to because the operating systems are different? As mentioned, I attempted to make a restore on my friend's macbook that I purchased as a spare but when I tried, it came back saying "Different operating systems, cannot restore" or something to that degree. Is there a way around this? Do I have to somehow downgrade the OS on my new machine?
Luckily, I use iTunes for all my movies/music & Adobe Creative cloud so I can easily restore those on any machine but my desktop personal data, photos, etc are on the Time Machine restore. Help me if you can, thanks in advance!

If you live near an Apple Store, make a Genius Bar appointment to have the computer tested. Supposedly there is no charge for testing. They can also give you an estimate.
Genius Bar Reservation US

How do I know which id to delete and insure time machine restore?

I had a glitch on my computer of the screen going black at random. I also had a recall on my imac for the segate drive which was replaced once. I brought it to the apple store after a week then determined there was no recall on my new drive and reinstalled Mt Lion to get rid of the black screen issue. Now here is the problem i got home and plugged in my ext drive for a time machine restore. I restored everthing using migrate assitant except the applications and desktop. I was asked to create another user name for the transfer. I don't understand why i had to do this so just slightly changed my id name. I now need to find the desktop data and can't find it under either names. I searched the drive direct and found the info is there but migrate assitant doesn't show it. I tryed to restore back some other files but it was me to changed the name of the restore using migrate assitant again. How many ids do I need? How do I blow way the 2nd id without gettting rid of my backup on the ext drive. I am so confussed now and can't figure out which admin id has the info and which doesn't . I don't even know if the info made it to the imac hard drive. help!!!

I had a glitch on my computer of the screen going black at random. I also had a recall on my imac for the segate drive which was replaced once. I brought it to the apple store after a week then determined there was no recall on my new drive and reinstalled Mt Lion to get rid of the black screen issue. Now here is the problem i got home and plugged in my ext drive for a time machine restore. I restored everthing using migrate assitant except the applications and desktop. I was asked to create another user name for the transfer. I don't understand why i had to do this so just slightly changed my id name. I now need to find the desktop data and can't find it under either names. I searched the drive direct and found the info is there but migrate assitant doesn't show it. I tryed to restore back some other files but it was me to changed the name of the restore using migrate assitant again. How many ids do I need? How do I blow way the 2nd id without gettting rid of my backup on the ext drive. I am so confussed now and can't figure out which admin id has the info and which doesn't . I don't even know if the info made it to the imac hard drive. help!!!

My Macbook Pro was stolen, and I have replaced it with a Macbook Air. New hard drive is too small for a Time Machine restore. How do I restore my more-expensive apps (ie iWorks) on my new Macbook without repurchasing them?

My Macbook Pro was recently stolen, and I have replaced it with a Macbook Air. I attempted to simply do a restore from the Macbook Pro's Time Machine backup, but since the new Macbook Air's hard drive is significantly smaller, a Time Machine restore was not possible. I even tried to choose only settings or only my User Profile (option) when restoring, but the backup was still too large to do a restore onto the new machine. How do I restore my more-expensive apps (ie iWorks) onto my new Macbook without repurchasing them? Also, I reaad somewhere that if you went to the Mac App Store and attempted to repurchase the app and clicked BUY, it would simply alert you that you have already purchased the app (and trigger a re-download)... NOT THE CASE... So I just dropped another $19.99 for a second copy of Pages... Not my intention....
Any help would be greatly appreciated.
LM

you should get a usb backup drive as well. time machine has limited use in my eyes. it saves things. but older things can be errased ad space drops without telling you
nothing beats data redundancy. 2 saves is. 1. and 1 is none
im personally not fond of time machne though i use it only for a recovery parameter for a mac
id never ever myself consider time machine a genuine data backup tool. though most do consider it as such
drive clones such as superduper and carbon copy cloner can clone your entire drive for emergency recovery. and you can boot from them as well o. another mac

Is it possible to boot or Time Machine restore from an external Thunderbolt disk drive?

(There are several questions - search for "?".)
I purchased a Seagate Backup Plus for Mac Desktop Drive 3 TByte with default USB 3.0 interface, and also acquired the Seagate Thunderbolt Adapter for Backup Plus Desktop Drives and Thunderbolt cable.
I do a redundant backup to the Seagate Drive using both Carbon Copy Cloner (nightly) and Time Machine (hourly) using its Thunderbolt adapter. BTW: One never knows when Time Machine will choke - see discussion titled, "UPDATED: Serious Time Machine bug on Mountain Lion", which I had; Rest In Peace Pondini (James Lewis Pond).
Booting from the external Seagate Backup Plus via Thunderbolt inteface from System Preferences -> Startup Disk:
I select the Time Machine OS X, 10.8.5 Startup Disk (Thunderbolt attached drive), click Restart, confirm my choice, the computer reboots, however, it reboots from the internal Macintosh HD OS X, 10.8.5, NOT the selected external Thunderbolt drive. The SSD drive was used as the Startup Drive, not the selected external Time Machine volume as indicated by the display free disk space command (df(1)) and seeing that the Macintosh HD OS X, 10.8.5 volume is mounted as root. That is very deceptive in that both the internal and external drives will appear in the same manner from a GUI point of view! OS X doesn't even inform me that it did not boot off the selected volume. This is the first half of the problem, that is, Is it possible to boot from an external Thunderbolt disk drive? In my case, the answer is deceptively No. Can anybody else boot off a Thuderbolt attached disk drive? Note that if I remove the Thunderbolt adapter, and attach the drive via its USB 3.0 cable, the MBP boots off the external Seagate Backup Plus just fine, as is expected.
Booting from the external Seagate Backup Plus via Thunderbolt inteface from boot-time "Option - Select startup disk" method:
When I restart the MBP using the startup Option key to select the startup volume, the externally connected Seagate drive ONLY SHOWS UP if it is attached with the USB 3.0 cable, not when it is attached with via the Thunderbolt interface. Can anyone else boot off a Thunderbolt drive with the startup Option key sequence? At least the MBP doesn't deceive me in this case - I know right away that the external Thunderbolt drive is not an option when connected as such.
Time Machine restore from the external Seagate Backup plus via Thunderbolt interface from the "command-R - Recovery Parition" method:
After booting from the recovery partition, I attempt to perform a Time Machine restore from the Thunderbolt connected Seagate Backup drive. When Time Machine attempts to present me with a viable backup Time Machine volume, the external Thunderbolt drive is never offered as an option. So I switch the Time Machine volume to use its USB 3.0 interface, and then Time Machine displays that drive as an option, and the MBP proceeds with the restoration as expected. The interesting thing to note is that while booted in the recovery partition via the Thuderbolt cable, the MBP Disk Utility may be selected, and the Thunderbolt attached drive may be operated on just fine. Can anybody else restore their MBP using Time Machine and the Recovery Partition via the Thunderbolt interface?
This is also a big problem for me in that I am forced to restore my MBP via Carbon Copy Cloner using the USB 3.0 interface, because I cannot even boot off that volume's Thunderbolt interface. Of course, the option may be that I could use yet another eternal USB 3.0 drive, boot from it, and then use Carbon Copy Cloner to restore the Macintosh HD via the aforementioned drive connected by a Thunderbolt cable, but that is less than ideal and not elegant, so I'm not going there.
Another side issue is that the commercially available program, TechTool Pro 7's eDrive, which I installed on the Time Machine volume, will not boot off that eDrive as advertised, but I won't got through those steps here, because that would be beyond the scope of this issue, however, I must say, It does not work either when the Time Machine volume is connected via the Thunderbolt interface, but works just fine when connected via the USB 3.0 interface.

If this helps anybody else make a decision about whether to consider Apple because of Apple's superior customer service:
Apple sells this entire line of drives right in their store, from 1TB to 4TB. I spent 1 and 1/2 hours, yesterday, confirming that the 3TB model IS NOT 100% Thunderbolt compliant. A MBP cannot boot, nor can it Time Machine restore from this drive, though EVERYTHING about the drive is normal.
Apple's South Coast Plaza store management had at least two responses to me personally about how to proceed:
1. Buy a different drive from another drive manufacturer, and to attempt to return the drive to COSTCO. A lead genius suggested going with GTech drives, for instance.
2. Wait for Seagate to fix their problem.
I told Apple management in the store that the drive is advertised as Mac Compatible (see picture) and that it is advertised as being a Thunderbolt drive (see picture). I pressed management that my purchasing decsion to get the best possible MBP Retina was based on the availablity of Inexpensive Devises (raID), and that not having this complete compatibility is a show-stopper for my needs, and that I wanted a refund. Their response? They needed to talk with "Merchendising" to see if they are on or off the hook for these kind of 3rd party assertions, and would get back to me.
I am not holding my breath.
Note: I do not hold this against the Geniuses that helped me, nor against the management I've dealt with, nor the upper level engineers that I've corresponded with through Apple Care - their problem solving skills were helpful - although I could have arrived at similar conclusions given enough $$$. (For instance, try a Lacie TB drive and see if that works - we did, and it did not work. Or, we have a different TB cable and a different TB adapter, let's try those - we did, and it did not work.) I blame myself for not doing enough homework before going with Apple's solutions.

Time Machine restore stuck at 99%

Similar Messages

Maybe you are looking for