ceet12

Q: Repair disk permissions help

Hello all,

im fairly new to the macbook and have been reading up on repairing disk permissions as the mac has started to slow down in time

 

the problem i have is i opened disk utility

 

and ran verrify disk permisions, it found problems, so i restarted and held comand and r and booted into the recovery console

 

from there, i chose disk utilities and ran verify disk again, again it found problems, so i ran repair disk permisons, that came  back and repaired succefull,

 

so just to check i then vefried the permisons again, and once again it found the same problems, so i then re - repaired the permisions, and again it cam back succefull

 

again i double checked and once again it found the same problems , so im going round in a loop here the problems arnt actually properly fixing?

 

 

how can i sort this out?

 

any help would be appreciated!

 

regards

MacBook Pro (15-inch Late 2011), Mac OS X (10.7.4)

Posted on Sep 25, 2012 8:26 PM

Close

Q: Repair disk permissions help

  • All replies
  • Helpful answers

  • by Niel,

    Niel Niel Sep 25, 2012 8:28 PM in response to ceet12
    Level 10 (314,589 points)
    Mac OS X
    Sep 25, 2012 8:28 PM in response to ceet12

    If running the repair permissions function once doesn't fix whatever issue you're experiencing, no amount of further runs will; look for other causes of that issue.

     

    (70193)

  • by frederic1943,

    frederic1943 frederic1943 Sep 25, 2012 8:56 PM in response to ceet12
    Level 6 (9,985 points)
    Sep 25, 2012 8:56 PM in response to ceet12

    Check out this article http://support.apple.com/kb/TS1448

  • by ceet12,

    ceet12 ceet12 Sep 25, 2012 9:07 PM in response to frederic1943
    Level 1 (0 points)
    Sep 25, 2012 9:07 PM in response to frederic1943

    hi thanks for replies, my errors are very simlar to what fredrick posted but not exact, i checked my permission errors to the ones in the logs apple described they are very simlar but are not mentioned these are my permission errors

     

    """

    Verifying permissions for “Macintosh HD”

     

    Permissions differ on “System/Library/CoreServices/Menu Extras/Displays.menu”; should be drwxr-xr-x ; they are lrwxr-xr-x .

     

    Permissions differ on “System/Library/MonitorPanels/Arrange.monitorPanel”; should be drwxr-xr-x ; they are lrwxr-xr-x .

     

    Permissions differ on “System/Library/MonitorPanels/Display.monitorPanel”; should be drwxr-xr-x ; they are lrwxr-xr-x .

     

    Permissions differ on “System/Library/MonitorPanels/Profile.monitorPanel”; should be drwxr-xr-x ; they are lrwxr-xr-x .

     

    Permissions differ on “System/Library/PreferencePanes/Displays.prefPane”; should be drwxr-xr-x ; they are lrwxr-xr-x .""""""

     

    i dont no whether this is a cause for concern as thiese exact permission errors dont seemed to be mentioned in the article?

     

    any help would greatly be appreciated..??

     

    thanks

  • by AnalogFile,

    AnalogFile AnalogFile Oct 23, 2012 2:16 AM in response to ceet12
    Level 1 (0 points)
    Oct 23, 2012 2:16 AM in response to ceet12

    Those messages are in fact quite similar to the ones Apple mention in the KB.

     

    All the examples you posted are instances of the same symptom: the BOM states a given path is supposed to be a directory but it actually is a symlink to a directory.

     

    A possible cause of this is when something was installed that did not foresee upgrades that would leave multiple versions installed at the same time, then the development team eventually decided that a new version would be needed to co-exist with the old one and such a new version has been installed. The old BOM file still report the directories (or files) as not being symlinks but the new installation actually moved the old data to a directory specific for the old version, installed a new version and then changed the old directory (aka the "unversioned" or "current" path) to a symlink to the latest installation.

     

    You can safely ignore these differences.

     

    While in the past running permission repair used to be a very important periodic maintenance routine, nowadays it's rarely needed and even more rarely useful. It still is a good idea to run it right before and after an important operating system patch update, but it's not really necessary.

     

    It's very common (and has been for a long time) for the tool to report differences, say they have been repaired, and then, if run again, to report the same differences. In those cases you can generally ignore those differences. Only if the repair tool says it failed to repair something you should be concerned.