Repairing permissions again

I'm having trouble repairing permissions with disk utility. It's these permissions that won't seem to repair if you have any suggestions I would appreciate them.
Thank you, Jack.

Unless you are having problems with your Mac, there is no reason to repair permissions repeatedly. You can ignore the messages, nothing to be concerned about. Repairing permissions is used for troubleshooting.

Similar Messages

  • I repair permissions, run Onyx, repair permissions again, but doesn't work

    The same permissions--a large number of them--need re-repairing again after each of these.
    What's wrong here?

    permissions messages you can safely ignore

  • New Mac Mini and Repairing Permissions

    I've been having trouble with my Mail program and thought I would repair permissions to see if that would help. I ran disk utility from my internal hard drive and ran repair permissions. Apparently it found several permissions to repair, so I thought I would run repair permissions again and the same list appeared. Running a third time and the same list appeared again.Do these permissions ever get repaired? What do I do from here? Should I repair permissions after booting up off of my original system disk? This Mini is only a couple of weeks old and I'm already having problems with Mail and repairing permissions.
    rskover

    Thank you Tim but the computer is packed back waiting for TNT to take it back to Apple. I don't have time to play with permissions, the permissions are OK in the old computer.
    This is what may have been your problem. The permissions on your old computer may not have matched the new computer. I think you gave up before the penny dropped.
    They sell the computers very expensive and I think they would have to improve quality.
    I am unsure how that can be one of your gripes as when the cube came out it was way overpriced in comparison to their other desktops. That did not stop your or I getting one then.
    Your issue was a software problem not a hardware problem so no matter what kind of mac you had it would have needed troubleshooting.
    The quality of the new mac mini far exceeds that of the cube. Try playing 1080P high definition media on your cube, or even 480P for that matter. Try outputting 5.1 surround sound from your cube without the addition of a firewire audio interface.
    I know how frustrating it can be when something just does not seem to work. I have encountered this a few times in my work. However sometimes I just have leave it come back with fresh eyes and try other approaches and I succeed.
    What you need to appreciate installing an upgrade should be planned for any eventuality. In business upgrades are scheduled to have the minimum impact on the workplace. That being said I have worked 48 hrs solid over a weekend getting systems up for a monday morning. They are not always straightforward.

  • Repair Permissions Error (Close to Runs too long, No Progress Bar)

    I have gotten this Repair Permissions error at least 10 times:
    Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
    One Internal Hard Drive, Erase, Install from scratch using Retail 10.5 DVD.
    Quad 266.
    It is similar to Repair Permissions takes forever with no progress bar, I get the Barber Pole for about 10 minutes and then it finishes with the above error. It seems like it is hanging trying to deal with the problem file and can't repair it.

    I ran REPAIR PERMISSIONS again after installing Acrobat updaters.
    At first I quit because it appeared to be hung.
    I re ran it and came back later to this:
    Repairing permissions for “105_HD”
    Stopped by user
    Permissions repair complete
    Repairing permissions for “105_HD”
    Warning: SUID file "usr/libexec/load_hdi" has been modified and will not be repaired.
    Warning: SUID file "System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources /DiskManagementTool" has been modified and will not be repaired.
    Warning: SUID file "System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Reso urces/Locum" 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/PrivateFrameworks/Admin.framework/Versions/A/Resources/readconf ig" has been modified and will not be repaired.
    Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/writecon fig" has been modified and will not be repaired.
    Warning: SUID file "usr/libexec/authopen" has been modified and will not be repaired.
    Warning: SUID file "System/Library/CoreServices/Finder.app/Contents/Resources/OwnerGroupTool" 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.
    Permissions repair complete

  • Disk Utility Repair Permissions ?

    Hello,
    I'm experiencing a persistent disk permissions repair issue using disk utility.
    With each re boot I get the following needing to be repaired...
    "Group differs on "private/etc/cups", should be 0, group is 26."
    I repair and re-run Repair Permissions again to find all is ok - however it comes back again when I re-boot.
    What can I do to get it to go away and what is it?
    thank you for your time.

    Reports of "spurious" information in Repair Permissions are wide enough that there are Apple articles on the reports for Jag and Panther (like here. Admittedly, they are much fewer in Tiger and Leo.
    "cups" is a printing subsystems, so some driver you've installed may be "taunting" Disk Utility. If you can print, you're OK.

  • Repair permissions taking forever

    I repaired disk permissions and then
    I installed Leopard without any problem.
    Then did software updates.
    Now, I'm repairing permissions again,
    but this time it's taking forever to complete.
    I've been stuck at "Repairing Permissions.Estimated time: calculating" for nearly 15 minutes and counting.
    The progress bar next to this message is less that 1/4 in blue.
    Is something wrong?!
    please, say it isn't so!!
    Message was edited by: teresita

    Yes, repair permissions takes MUCH longer in Leopard. I've upgraded three systems and they all take what seems like 10 - 15 minutes (10.4.11 took less than one minute). Guess we were "spoiled" with previous versions

  • Repair Permissions problems after Software Update (10.5.7)

    I ran Software Update this evening.
    I selected the following Updates:
    Mac OS X Update 10.5.7 (I was at 10.5.6)
    iTunes 8.1.1
    Airport Utility Software Update 5.4.1
    On restart, there was a warning icon (circle with diagonal line) and the gear kept spinning. No response at that point.
    I called Apple and following his instructions..... Booting from the Leopard disk I/we/it repaired permissions and verified disk and then restarted and all seems well.
    However, on the repair permission after this warning there were a number of permission problems reported and I just ran Repair Permissions again and they persist. AppleCare said those error reports would most likely remain but that they will not cause any problems.
    I'd appreciate an assessment by anyone who is an expert in this area.
    Thank you.
    The log from Permission repair follows:
    Repairing permissions for “Peanut Butter HD2”
    Reading permissions database.
    Reading the permissions database can take several minutes.
    Warning: SUID file "System/Library/Filesystems/AppleShare/afpLoad" has been modified and will not be repaired.
    Warning: SUID file "System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources /DiskManagementTool" has been modified and will not be repaired.
    Warning: SUID file "sbin/umount" has been modified and will not be repaired.
    Warning: SUID file "bin/rcp" has been modified and will not be repaired.
    Warning: SUID file "usr/bin/quota" has been modified and will not be repaired.
    Warning: SUID file "usr/bin/rlogin" has been modified and will not be repaired.
    Warning: SUID file "usr/bin/rsh" has been modified and will not be repaired.
    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-- .
    Permissions differ on "System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/AppleMobile DeviceHelper.app/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/AppleMobile Sync.app/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions repair complete

    Norm,
    I'd appreciate an assessment by anyone who is an expert in this area.
    According to Apple: Mac OS X 10.5: Disk Utility's Repair Disk Permissions messages that you can safely ignore
    ;~)

  • CANNOT REPAIR PERMISSIONS - pls help!

    While booted from my restore disk (with Disk Utility Open & attempting to repair permissions), D.U. goes about 33% of the way & stops/displays the following onscreen message: Disk Utility Internal Error
    Disk Utility has lost it's connection with the Disk Management Tool and cannot continue. Please quit and relaunch Disk Utility.
    I used DiscWarrior to rebuild the directories & then ran TechToolPro 4 from my eDrive to check Volume Structures (came up clean).
    For the heckuvit, ran D.U. from my Apps Utility Folder. This time it did complete, making some changes. Ran a second time. Results of each are shown below.
    Repairing permissions for “Panther:Operating”
    Determining correct file permissions.
    We are using special permissions for the file or directory ./Library/ColorSync/Profiles/Displays. New permissions are 16893
    We are using special permissions for the file or directory ./Library/ColorSync/Profiles. New permissions are 16893
    Permissions differ on ./Library/ColorSync/Profiles, should be drwxrwxr-x , they are drwxrwxrwx
    Owner and group corrected on ./Library/ColorSync/Profiles
    Permissions corrected on ./Library/ColorSync/Profiles
    We are using special permissions for the file or directory ./System/Library/Filesystems/cd9660.fs/cd9660.util. New permissions are 33261
    We are using a special uid for the file or directory ./private/var/at/jobs. New uid is 1
    User differs on ./private/var/at/jobs, should be 1, owner is 0
    Owner and group corrected on ./private/var/at/jobs
    Permissions corrected on ./private/var/at/jobs
    We are using a special uid for the file or directory ./private/var/at/spool. New uid is 1
    User differs on ./private/var/at/spool, should be 1, owner is 0
    Owner and group corrected on ./private/var/at/spool
    Permissions corrected on ./private/var/at/spool
    Permissions differ on ./private/var/log/install.log, should be -rw-r--r-- , they are -rw-r-----
    Owner and group corrected on ./private/var/log/install.log
    Permissions corrected on ./private/var/log/install.log
    Permissions differ on ./private/var/log/wtmp, should be -rw-r--r-- , they are -rw-r-----
    Owner and group corrected on ./private/var/log/wtmp
    Permissions corrected on ./private/var/log/wtmp
    The privileges have been verified or repaired on the selected volume
    Permissions repair complete
    This is from D.U. in Apps folder run while booted from startup drive.
    Repairing permissions for “Panther:Operating”
    Determining correct file permissions.
    We are using special permissions for the file or directory ./Library/ColorSync/Profiles/Displays. New permissions are 16893
    We are using special permissions for the file or directory ./Library/ColorSync/Profiles. New permissions are 16893
    We are using special permissions for the file or directory ./System/Library/Filesystems/cd9660.fs/cd9660.util. New permissions are 33261
    We are using a special uid for the file or directory ./private/var/at/jobs. New uid is 1
    We are using a special uid for the file or directory ./private/var/at/spool. New uid is 1
    The privileges have been verified or repaired on the selected volume
    Permissions repair complete
    This is from D.U. in Apps folder run while booted from S.U. drive (run a second time).
    Then tried once more, booted from the restore disc & STILL it stops a 3rd of the way & displays the same onscreen message.
    Why is this happening & how can I resolve it?
    Don

    This has to do with a problem with the latest update and Panther and iTunes.
    Tip offered by Kappy and others in the 10.3& earlier Forum;
    1) Move iTunes onto the Desktop.
    2) Run Disk Utility
    3) Go to HD>Library>Receipts and trash all iTunes .pkg files EXCEPT for iTunesX.pkg and iTunesPhoneDriver.pkg
    4) empty Trash.
    5) move iTune from Desktop back to 'Applications'.
    Hey presto. you should now be able to repair permissions again.
    Offered by Bee;
    Kappy, et all . . .
    This was posted earlier today . . .
    I'll have to get the author's name, sorry don't have it now.
    It seems that it may not necessary to pull iTunes out of the App folder:
    Did you recently update your iTunes?
    If so, that seems to have caused a bit of a problem with Panther.
    If that is the case,
    Go to HD>Library>Receipts and trash all ITunes .pkg files
    EXCEPT iTunesX.pkg and iTunesPhoneDriver.pkg. Then see if you can repair permissions.
    Be very careful here, be sure to leave the last two there!
    Cheers!
    DALE

  • Repair Permissions runs for hours

    Following an update from Mavericks to Yosemite 10.10, I find that when I use the Disk Utility to repair permissions, it runs for hours, seemingly repairing every one of the 680,000 files on the iMac. If I reboot, and repair permissions again, it begins the same long process all over again. Should I re-install Yosemite from an online source?

    Does the last line of output say that permission repair completed successfully? If so, what you see is normal. Repairing permissions is a waste of time and always produces reams of meaningless warnings.

  • Disk Error during Disk Utility Repair Permissions

    I was wondering if anybody else has experience a Disk Utility Internal Error while repairing the permissions on their system disk. What did they do to correct this issue?
    A snapshot of the error can be viewed at:
    http://www.enabled.com/~noah/pictures/Picture1.pdf
    Thanks in advance.

    Tom
    I sympathise if you are on dialup! Here is the post you need (originally posted by Mac Fool):
    Just to catalogue the solutions listed above
    Here's what I did, and it worked fine.
    1) Move iTunes onto the Desktop.
    2) Run Disk Utility
    3) Go to HD>Library>Receipts and trash all iTunes .pkg files EXCEPT for iTunesX.pkg and iTunesPhoneDriver.pkg
    4) empty Trash.
    5) move iTune from Desktop back to 'Applications'.
    Hey presto. you should now be able to repair permissions again.
    HTH
    Just as Beavis posted above
    BTW, the link "here" does take me directly to the post, but clearly it loads the entire topic first.

  • Repairing permissions - repeated problems

    I've been trying to install Leopard for a few dayson my emac.
    Due to getting spurious 'damaged disk' messages, I've tried it using the installer disk in the emac itself, in an external DVD drive and connected via firewire to my ibook.
    I managed to install it eventually,and then couldn't repair permissions.
    I decided to erase and install, and I've come up against it again: trying to repair permissions, the disk utility still says repeatedly 'the underlying task reported failure on exit'. This is on a newly-erased hard disk, just-installed version of 10.5.1, nothing else done to the computer since then.
    Any clues?

    I ran repair permissions again a few more times, and it finally worked.
    Then I decided to restart to install 10.5.2.
    I got a kernel panic, which repeated every time I tried to startup.
    Eventually, I decided to erase and install, again, after running DiskWarrior too, and now I'm getting the 'damaged media' message in various forms.
    I can't believe it's meant to be this difficult.

  • 500 Pages Of Repaired Permissions???

    I just repaired permissions and it kept going and going. I thought I better keep this so copied into Word. Turned out to be over 500 pages.
    I Verified Disk and it did not bring up any problems. I repaired permissions again and nothing.
    Should I be worried or is that normal for some reason to bring up sooooo many bad permissions???
    Should I run any other checks?
    thanks,
    frank

    As a matter of fact I did... I moved a ton of vid files off the MBP to an external then did a bunch of transfers using two different externals then added about 40 vid files to the MBP.
    And I did see a ton of Quick Time go by in the repaired permissions. Would that all explain it?
    thanks,
    frank

  • Won't boot after I repair permissions

    2007 iMac 20". Installed Lion and it worked fine until yesterday. Acting a little wonky so I verified the disk and repaired permissions in Disk Utility and now it will not boot up past the grey apple logo screen with the spinning icon. I tried booting off of a Lion recovery disc and repaired the disk and repaired permissions again. All to no avail. Exact same problem. Finally I had to restore my system off of my latest Time Machine backup to get it functional again. Any clue what is causing my issue?

    repair via SUS
    edited:
    connect to wall charger open sd card flap and push off button until phone vibrate..let it charge then perform software repair
    Some will call me fatalist And some will call me freak
    But hidden in my throwing fist The fortune that I seek-- Amon amarth

  • Repairing permissions taking hours

    I reluctantly downloaded 10.6.6 to my mid 2010 MBP and immediately repaired permissions. I started over two hours ago and it still says two minutes, but seems to be stalled. It hasn't actually stalled because every minute or two it will say something like Library support media blah blah blah Spanish lprog should be 80 group is 0. It seems to have been going through every language known to man, and a few that aren't. How normal is this? I know when I originally installed SL I should have deleted all the languages, but I didn't and now I'm paying the price.
    Do I just let it run for the next few hours, or can I stop it, use Monolingual and then repair permissions again? Would that be of any help?

    I rebooted and PR only took a couple of minutes. However, I was then told my password had expired, of course it wouldn't accept my old one, so I had to reset it and delete the discussion .plist. Things are pretty much back to normal for the moment, although there are still some forums that won't accept any password, but it'll be sorted one way or the other.
    I didn't use Monolingual, rebooting was the solution.

  • Why does "repair permissions" actually creates more repairs when again.

    When I use Disk Utility repair permissions, I run it a second time and there were more instances than noted in the initial run. 13 the first time and 22 the second. To double check, I rebooted my MBP to make sure it wasn't an issue with a running program. The same thing happened, I got 13 instances the first time and when I hit it again, I got 22. I find it hard to believe that by running "repair", more instances are created.
    Also, why are some things just not repaired?
    Thanks so much for any guidance.
    Sincerely,
    Skip

    Specifically, what "repair permissions" does is look at a bunch of files called "BOM files" or "Bill of Materials files", which is simply a list of what files where installed where and with what permissions. They are created by the Mac software package make that vendors use to build installation packages (if you've ever installed software that required you to run an installation program rather than just copy it to /Applications, that's what you have).
    When you run "repair permissions", it compares the file's permissions with what's in the BOM. If they aren't the same, it changes the file's permissions to whatever the BOM says they originally were. The idea being that something might have altered the permissions on a file file making it impossible for you to access and thereby messing up anything that requires access to the file. In practice, that doesn't happen too often.
    What does happen pretty often is that the software installer copies files and then changes permissions on them. Even the application may change permissions on the files. That's pretty common, and often necessary to the operation of a piece of software. So, despite doing a "repair permissions", some files and directories are going to simply defy having their permissions modified (particularly things like directories where log files are stored).

Maybe you are looking for