Cannot successfully run Repair Permissions

I've tried to run repair permissions after a software update, but it constantly fails to complete the task. I get this error:
"Disk Utility lost it's connection with Disk Management Tool and cannot continue"
Can someone offer advice?
Thanks!

If you've got 10.3.9 or earlier and recently updated to iTunes 6.02 then what seems to work for most people is:
Go to HD>Library>Receipts and trash all iTunes .pkg files EXCEPT for iTunesX.pkg and iTunesPhoneDriver.pkg
This will let you fix permissions as per normal, AND keep iTunes 6.02 in your Apps folder.
ATB
ian Waterston

Similar Messages

Problem: I have to run repair permissions to access the internet using safari, firefox or chrome on my mac pro. What can I do to fix the problem once and for all?

This is what I get when I run repair permissions in disk utility. Thanks for any assistance you can give.
Repairing permissions for “Macintosh HD”
Repairing permissions for “Macintosh HD”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pl.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pl.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pl.lproj/MainMenu.nib”
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pl.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pt_PT.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pt_PT.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pt_PT.lproj/MainMenu.nib”
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pt_PT.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pt.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pt.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pt.lproj/MainMenu.nib”
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pt.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/sv.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/sv.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/sv.lproj/MainMenu.nib”
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/sv.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/ru.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/ru.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/ru.lproj/MainMenu.nib”
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/ru.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/no.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/no.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/no.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/no.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/fi.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/fi.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/fi.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/fi.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/da.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/da.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/da.lproj/MainMenu.nib”
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/da.lproj/MainMenu.nib”
Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent” has been modified and will not be repaired.
Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent” has been modified and will not be repaired.
ACL found but not expected on “private/var/db/launchd.db/com.apple.launchd”
ACL found but not expected on “private/var/db/launchd.db/com.apple.launchd”
Repaired “private/var/db/launchd.db/com.apple.launchd”
Repaired “private/var/db/launchd.db/com.apple.launchd”
Permissions repair complete
Permissions repair complete

Would you care to tell us which version of Mac Pro, and which version of OS X, you are running? (It's not always safe to assume that a User is running Lion just because he posted in the Lion Forum.)

Possible to run repair permissions before mac fully boots?

Is it possible to use a keyboard shortcut during boot, type in some code, and run disk utiliy or repair permissions?
Cause I would like to run it but the powerbook wont fully boot and my install disk is in a different city.
Can I use anyones leopard install cd or does it need to be mine?
plz help
Message was edited by: wroth

VK and Kenichi are right. Permissions have changed so don't run repair permissions from a non-Leopard disk.
However, repairing permissions has really become a "magical elixir" that is supposed to solve all kinds of problems. It won't.
Apple's official recommendation is not to run repair permissions from the install disk because a software update could have changed permissions. In any event, if your machine won't boot, repairing permissions won't help. Repairing the disk might.
The HFS+ file system hasn't changed in Leopard. If your machine won't boot, and all you have is a Tiger disk, running disk repair should be safe. After all, it is perfectly safe to have both Leopard and Tiger on the same machine and Tiger can and will run disk repair on its own when it boots up.
Hopefully I've salvaged something from my technical reputation.

Problems with running Repair Permissions

ok,
everytime my powerbook stays on for a while (maybe 1 to 2 days without reboot), my mac slows down. When I look at my iStat Pro, I see almost all my memory in the "inactive" status and under CPU, a high percentage is under "user".
I run repair permissions in the disk utility and this frees almost all the memory from the "inactive" status to "free" and my mac goes a whole lot faster.
my problem is that i get the exact same permissions repair all the time. It says:
"Determining correct file permissions.
Permissions differ on ./private/var/log/secure.log, should be -rw------- , they are -rw-r-----
Owner and group corrected on ./private/var/log/secure.log
Permissions corrected on ./private/var/log/secure.log"
is there some way to fix this problem so that i don't have to run a permissions repair all the time??
thanks for any help.

It's just a log file. Don't worry about it.
Using Repair Disk to "free" memory is a waste of time. Your computer's total available RAM is always the sum of "Inactive" RAM and "Free" RAM. It may be useful for you to read Reading system memory usage in Activity Monitor.
Why reward points?(Quoted from Discussions Terms of Use.)
The reward system helps to increase community participation. When a community member gives you (or another member) a reward for providing helpful advice or a solution to their question, your accumulated points will increase your status level within the community.
Members may reward you with 5 points if they deem that your reply is helpful and 10 points if you post a solution to their issue. Likewise, when you mark a reply as Helpful or Solved in your own created topic, you will be awarding the respondent with the same point values.

When I run repair permissions I continue to get this message even after a full reformat and re-install of OS. "Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repai

When I run repair permissions I continue to get this message even after a full reformat and re-install of OS. "Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired."

Doug,
According to Apple, Mac OS X: Disk Utility's Repair Disk Permissions messages that you can safely ignore.

External drives won't mount after running repair permissions

None of my external drives will mount after running disk permissions. Drives work fine on my mbpro.
None of the external drives show up in disk utilities...
I've try shutting down and unplugging computer. even mini zip drives won't mount.
I'm running 10.4.11
PPC G5 2.3Ghz
Thanks for any help..

Repairing Permission only deals with installer receipts and system components. Not with mounting or accessing hard drives.
Have your run Apple DU First Aid? Disk Warrior? Only use latest version for your OS.
Are you trying to clone your system to external and then repairing permissions? trying to boot from them?
If cloning, make sure the "Ignore Ownership" flag is unchecked before cloning (but do repair permissions on external drives you intend to boot from, such as a Firewire drive).
What type of cases and interface are these?

Leopard on MacBook and MacBook Pro / running repair permissions

I upgraded both MacBook and MacBook Pro without major problems. I have been trying to repair permissions on the Mac Harddrive , and just get the spinning wheel. I have in the past run Onyx to perform routine maintenance tasks, but did not want to run any third party programs in relation to maintenance. Do I need to run it from the text tool disc? I never used to have to run it from disc.
Thanks.
Jon Pousette-Dart

I used Cocktail, Onyx, and YASU before Leopard, but had some problems with repairing disk permissions since upgrading to Leopard. Didn't know Cocktail had upgraded to Leopard. I'm impervious to snide remarks from self proclaimed experts.
We run a studio here north of NYC ( which is a standard ProTools HD Accel facility and won't touch Leopard for sometime) Leopard is on two laptops which seem to run good but slower since the Leopard upgrade. Might try the upgraded Cocktail.
As far as Beta Testors, That was the verbatim words out of level two Mac support. Their words not mine. Not one of the guys I talked to even planned on running Leopard on their own machines, as none of us in the pro community will either.
Having said that, it's on two of my laptops, just not the machines I run to do final mixes on.
Jon Pousette-Dart
www.pousette-dart.com

10.3.9: G3 iMac won't run 'Repair Permissions' from Panther Disk!

I upgraded the memory to 1024 mb RAM and reinstalled Panther yesterday after leaving it on the shelf for a couple of years due to numerous problems running it on Kihei and Pismo (both with 256 mb RAM). The loading process went well; I ran the following utilities after loading all of the updates:
TechTool 4.0.1
Disk First Aid from Panther disk
Repair Permissions from Panther Disk
Reset NVRAM, PRAM and OF
TechTool showed no problems and Disk First Aid said a repair was made. The first time I attempted to repair 'permissions' the process seemed to be about half way complete when it stopped and displayed the following error:
'Disk Management Tool' has lost contact with Disk Utility, close function and restart Disk Utility' or something to this effect.
Every attempt afterwards results in the same error message coming up almost immediately. iMac seems to be running properly at the moment; is it about to crash again like it did so many times in the past before I reverted to Jaguar? Any insight or advice will be welcome. I will post a copy of this on the 10.3 Panther board too.

Road Hazard: Try the instructions in this article. It is not possible to use the Panther installation disks to repair the permissions on a system which is experiencing this issue.
scapesuiter: A Kihei is one of the models which make up the first slot-loading iMac machines. These came out in October 1999 and were discontinued in July 2000.
(15253)

Neat Trick! Free memory run Repair Permissions...

Ok, this one baffles me, I'm wondering if its just my MBP setup or if this will work for anyone. I noticed that if I run Disk Utility and Repair Permissions after starting up I free up almost 300megs of memory. Yes 300 MEG! Even if there are no permission problems to fix...
When I start up I have around 1112 Meg free memory and another 300-400 of used inactive memory. If I run DU and repair permissions my free memory shoots up to 1442 MEG Free.
Could someone else give this a try and let me know if the same happens for you. If it does I'd sure like to know why.
I realize this isn't an earth shattering thing here but it is a little puzzling, at least to me...
Would love to hear others results with this...
Cheers,
Peter

The only app that appears to display all running processes (if you can get them to display properly) is "top." Open the Terminal and run top at the prompt. If you have the Developer Tools installed you could try using the included utility called BigTop. It's likely that the processes with lowest PIDs are the ones run at startup. I don't know the specific processes but I do know the startup sequence of events:
The first thing that runs at startup is the BootROM. It contains the POST or Power-On Self Test that checks basic hardware, sets the initial states for the CPU, RAM, and crucial hardware interfaces. It also verifies RAM. If the machine passes POST then you will hear the normal chime. If not you will hear one of five beep errors: one beep means no RAM installed; two beeps means the RAM is incompatible; three beeps means there are no good memory banks; four beeps means there is no good image in the BootROM; and five beeps means the processor is not operable.
Next is the initialization of Open Firmware which also checks for startup modifier keys (like OPTION or SHIFT.)
After initialization the Mac OS X system is located and control is transferred to BootX which initializes the kernel environment and drivers needed to boot the system. It also starts up the kernel initialization process. When loading the kernel environment BootX also attempts to load any previously cached set of device drivers. This is what's going on when you see the spinning gear on the startup screen.
Next the kernel initializes the I/O kit and starts launchd. Launchd manages all the system daemons for both the system and individual users.
If you open Activity Monitor then click on the PID column to sort the PIDs in ascending order, then from the drop down menu select All Processes, Hierarchically. You will see the order of processes handled by launchd which is the first process run after initialization. Process 0 is the kernel_task.
After launchd executes it runs the /etc/rc script that performs basic system initialization which in turn launches SystemStarter that runs the contents of the startupitems folder. Configuration data are stored in the /etc/hostconfig file.
Next comes the Login Window process which loads the user environment, then the Dock, Finder, and SystemUIServer followed by any Login Items. If this is an installation in progress it will also launch the Setup Assistant.
This completes the startup process.

Running repair permissions

I ran repair permissions and had this line come up at the end of detail list:
Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
is this something I should be concerned about? If so is there anything i can or should do?
Thank you in advance for any assistance concerning this.

Hi Norvegr
{quote:}is this something I should be concerned about? If so is there anything i can or should do?{quote}
No and No!
Have a look at > http://support.apple.com/kb/TS1448
Dennis

My MacBook Pro is running very slow. I've run repair permissions without positive result. Does anyone have any ideas?

My MacBook Pro (2010) is runnign very slow. This came on all of a sudden. It opens, closes, reboots, etc., all much slower than ever before. I have used the repair disk permissions without any positive result. Does anyone have any ideas?

First, back up all data immediately, as your boot drive might be failing.
Take these steps when you notice the problem.
Step 1
Launch the Activity Monitor application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Activity Monitor in the icon grid.
Select the CPU tab of the Activity Monitor window.
Select All Processes from the menu in the toolbar, if not already selected.
Click the heading of the % CPU column in the process table to sort the entries by CPU usage. You may have to click it twice to get the highest value at the top. What is it, and what is the process? Also post the values for % User, % System, and % Idle at the bottom of the window.
Select the System Memory tab. What values are shown in the bottom part of the window for Page outs and Swap used?
Next, select the Disk Activity tab. Post the approximate values shown for Reads in/sec and Writes out/sec (not Reads in and Writes out.)
Step 2
You must be logged in as an administrator to carry out this step.
Launch the Console application in the same way as above. Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left.
Post the 50 or so most recent messages in the log — the text, please, not a screenshot.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into a message.
Important: Some personal information, such as your name, may appear in the log. Edit it out before posting.

"Repair Permissions" won't run after undating to 10.5.5

I just updated to 10.5.5 and then tried to run Repair or Verify Permissions from the 10.5 startup disk. It get about 1/4 of the way through and then stops (freezes). I even let it go for 10 minutes and still nothing. It will let me run Verify Disk and says that the disk is okay.
Any ideas as to what may be causing this problem?

first, you shouldn't be running repair permissions from the install DVD. when possible it should always be done using disk utility on the drive itself while booted normally. secondly, permissions repair takes much longer in leopard. up to 40 minutes+ on older hardware. what you were seeing is normal. you just have to let it finish.
lastly, verifying permissions is a waste of time and you should always repair them right away.

Repair permissions runs then Mac shuts down

I have installed ilife 09 and since doing so my iphoto will not stay open. Also iphoto only displays about 10 photos of a possible 500. On another post I was told to run "repair permissions" in an effort to resolve this problem. While repair permissions runs my mac shuts off. Any clue as to what is happening?

Look in console to see why it is shutting down - I'm going go guess overheating - if so try cleaning your air vents to assure unobstructed air flow to the interior of the computer
LN

Repair Disk / Repair Permissions -- which first

If I want to run repair permissions or repair disk, which should I do first?
Does it matter?

"Repair disk" makes modifications to the structure of data on the disk itself. If there is an error, this really needs to be done first since the errors could manifest themselves as botched permissions, mangled files, etc. If the disk's integrity is actually compromised, the highest priority is to repair it. One thing to keep in mind is that certain repairs cannot be made on a mounted disk (such as the one you boot from), so for the disk repair procedure to work, you should boot of another disk (your OS installation disk, a bootable external hard disk, etc.). Even then, Apple's disk repair is curiously basic -- there's many errors it simply does not detect or fix and for that you need something like DiskWarrior. Mind you, disk errors like that shouldn't occur, and if they do you may have hardware issues to be concerned about.
"Repair permissions" compares file ownership and permissions in a directory to a list stored in the package bundles in /Library/Receipts. If there's a difference between what it finds in the file list stored in the receipt package, and the files on disk, it attempts to set the permissions and ownership of the file to what appears in the list (which should reflect the state of the file when installed). It doesn't do anything at all to preferences, user preferences, user files, logs, file created after and application is installed, etc.
Contrary to popular belief, repairing permissions doesn't generally do much for you. It should be pretty rare that it finds a difference unless you've really been mucking about, and generally when it does find something it's either because you explicitly changed the permissions or because there's some other problem where an application or disk issue is changing the permissions. The one time where it really makes sense, actually, is after you repair a disk issue.
It's common advice that people tell you to repair permissions as a step to address problems, but mostly because it's an easy thing to do. Similarly, zapping your PRAM is frequently advised when trouble-shooting, though the process of a cold-boot (complete power-off, then power back on a few seconds later) is generally the portion of that procedure that actually produces the desired result.

Plz help...problem w/ verify/repair permissions after software update

Hi,
I just ran the software update from the Mac menu and wanted to verify/repair permissions afterwards. First I used Onyx and when it was executing, the system would not respond after a couple of minutes. So then I tried Disk Utility and I get a message saying "Disk Utility internal error: Disk Utility has losts its connection with the Disk Management Tool and cannot continue. Please quit and relaunch Disk Utility." And I did, and the same message appears.
What else can I do?
Thanks.
PowerBook G4 15 Mac OS X (10.3.6)

Have just done software download - gone to repair permissions and have got same message. Running on 10.3.9. Anyone any ideas as to what is going on here. Did NOT run repair permissions before the update (Yes I know I should have done). Could this be a factor. There are a number of other threads on this forum concerning this exact problem - but so far have found no explanation or solutions.
Disk varified and reported OK. Mac seems to be operating OK. How does Disk utility "link" to Disk Management Tool?
Any help much appreciated.
Thanks

Cannot successfully run Repair Permissions

Similar Messages

Maybe you are looking for