Repair Disk Permissions: is it a safe operation ?

Hello,
I'm preparing for the 101 course and, reading about the Verify/Repair disk permissions utility, I wanted to test it on my mac.
I launched the verification on it and I see "lot" of unexpected entries (see below):
Verifying permissions for “Macintosh HD”
Permissions differ on “System/Library/User Template/ar.lproj”; should be drwxr-xr-x ; they are drwx------ .
User differs on “usr/share/collabd/coreclient/public/locales/zh_CN.lproj”; should be 94; user is 0.
Group differs on “usr/share/collabd/coreclient/public/locales/zh_CN.lproj”; should be 94; group is 0.
User differs on “usr/share/collabd/webauthd”; should be 94; user is 221.
Group differs on “usr/share/collabd/webauthd”; should be 94; group is 221.
User differs on “usr/share/collabd/webauthd/locales”; should be 94; user is 221.
Group differs on “usr/share/collabd/webauthd/locales”; should be 94; group is 221.
User differs on “usr/share/collabd/webauthd/locales/zh_CN.lproj”; should be 221; user is 0.
Group differs on “usr/share/collabd/webauthd/locales/zh_CN.lproj”; should be 221; group is 0.
Group differs on “Library/Java”; should be 0; group is 80.
Permissions differ on “Library/Java”; should be drwxr-xr-x ; they are drwxrwxr-x .
Permissions differ on “System/Library/User Template/cs.lproj/Pictures/iChat Icons”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “System/Library/User Template/hu.lproj/Pictures/iChat Icons”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “System/Library/User Template/tr.lproj/Pictures/iChat Icons”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
User differs on “usr/share/collabd/coreclient/locales/zh_CN.lproj”; should be 94; user is 0.
Group differs on “usr/share/collabd/coreclient/locales/zh_CN.lproj”; should be 94; group is 0.
Permissions differ on “usr/share/devicemgr/frontend/admin/zh_TW.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/zh_CN.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/ru.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/ko.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/nl.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/it.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/es.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/fr.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/de.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Permissions differ on “usr/share/devicemgr/frontend/admin/ja.lproj/app/javascript.js”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
Group differs on “Library/Documentation/Applications/iTunes/Acknowledgements.rtf”; should be 0; group is 80.
Permissions differ on “Library/Documentation/Applications/iTunes/Acknowledgements.rtf”; should be -rw-r--r-- ; they are -rw-rw-r-- .
Group differs on “Library/Documentation/iPod/Acknowledgements.rtf”; should be 0; group is 80.
Permissions differ on “Library/Documentation/iPod/Acknowledgements.rtf”; should be -rw-r--r-- ; they are -rw-rw-r-- .
Group differs on “.DS_Store”; should be 80; group is 0.
Permissions differ on “.DS_Store”; should be -rw-rw-r-- ; they are -rw-r--r-- .
User differs on “Applications/.DS_Store”; should be 0; user is 501.
Permissions differ on “Applications/.DS_Store”; should be -rw-rw-r-- ; they are -rw-r--r-- .
Group differs on “Library/Preferences/com.apple.alf.plist”; should be 80; group is 0.
ACL found but not expected on “private/var/root”
ACL found but not expected on “private/var/root/Library”
ACL found but not expected on “private/var/root/Library/Preferences”
Permissions verification complete
It seems to me that these are all related to system files, things that weren't changed by third-party applications or by me.
The question are:
- why an untouched system would have errors in the permissions ?
- is it safe, since I haven't got until now problems with permissions on that os, to repair these errors or it's better to leave everything as it is now ?
Ciao,
Nicola

Hello Nicola,
You raise a touchy area for discussion...some users on here are very opposed to repairing permissions, others are strongly in favor of repairing permissions before and after software installation.
The permission statements you see do not generally adversely affect the system but they are not the permissions disk utility has been told to expect. Those may be artifacts from the installation process and why we have been told in the past to always repair permissions after installing/updating the operating system.
Since you ran verification, if you run repair you will end up cleaning up a lot of this "discrepancies" with what disk utility wants to see.
Repair permissions is safe, and I tend to use it every time I upgrade or install software.
Ralph

Similar Messages

Safe to verify and repair disk permissions with SSD?

Is it safe to verify and repair disk permissions with an SSD installed?

Thanks.
Its just strange, as soon as I repair all my permissions, if I verify them again straight away, there are some that already need re-repairing

Safe To Repair Disk Permissions?

Is it safe to Repair Disk Permissions using Disk Utility in Snow Leopard? I could've sworn I read somewhere that you shouldn't do it. Maybe I imagined it.

You are probably thinking of fsck.
If you use that you can get some false error messages as explained here:
Tip: If you use a Mac OS X Extended (Journaled) formatted volume, such as with Mac OS X 10.3 or later, you probably won't need to use fsck. If you do use it for any reason, please be aware that benign error messages can appear.
If you're not sure how your volume is formatted and you can't start up from your Mac OS X volume to find out, type the following command in a command-line interface and then press Return: diskutil info /
If you see "File System: Journaled HFS+" returned, you have a Journaled volume.
http://support.apple.com/kb/TS1417

Archive, Repair Disk Permissions, etc. problems

I have problems trying to archive files/folders. I get an error message: "The archive's list of contents cannot be created." I tried repairing disk permissions and it would still have that error message.
Later, I decided to try to use Onyx, however, I couldn't access it and suggested to repair disk permissions and restart Onyx. I did that it still have that message. I later tried in another account, then in Safe Boot in my primary account and nothing changed. I can't even uninstall Onyx unless I repair disk permissions.
I seemed to have problems syncing my iPod Touch 2g with iTunes saying that it couldn't sync because there was another sync client. I'm not sure if this is also related.
It seems like that there is a system wide problem.

I did stumble over that same thread and attempted to follow it. Something didn't work. I wasn't sure where '/tmp' was and using Terminal to perform the operations somehow didn't solve it. After revisiting the thread you posted, I figured out what was tmp which was located on the Macintosh HD -there was /tmp. Then I followed the steps and voilà, the archive did work. Along with Onyx and everything else.
thanks!

Anyone clean their mac using the disk utility using the repair disk permissions??

anyone clean their mac using the disk utility using the repair disk permissions??

No. Threads don't hurt anything. If your computer is not functioning properly perhaps you need to try some basic maintenance. Let's start by having you do this:
Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
Next, try booting into Safe Mode then immediately restart normally. Safe mode is going to take a while so be patient. It's slow.
Next, create a new user account. Log out of your account then log into the new account. Try using iPhoto and the publishing button. Do they work now?
If you still have a problem, then do the following. If you don't want to go through the above then just start with the following and forget the others above.
Reinstall OS X without erasing the drive
1. Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Reinstall Snow Leopard
If the drive is OK then quit DU and return to the installer. Proceed with reinstalling OS X. Note that the Snow Leopard installer will not erase your drive or disturb your files. After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
Download and install Mac OS X 10.6.8 Update Combo v1.1.

New macbook pro, safari won't open and repair disk permissions did nothing to help

Safari starts, blue bar moves about an inch in search bar, then stops. Then nothing. Tried repairing disk permissions to no avail. Safari still doesn't open. Whatever os x that is installed on new macbook pro's, since just bought on Sunday 10-14-12, is the operating software. The apple store there is no user manual. Strange. So here we are on another, older macbook pro, able to go on internet and see what answers or diagnoses others have tried and trued.

3 days old?, just pack the machine up and tell them you want another one, that this one is a lemon.
They will likely take your word for it and just give you another rather than you demand your money back instead.
If you wait too long then they say you should have brought it back sooner, now have to wait until it's fixed, only to give you more problems later.

Constantly having to repair disk permissions after hanging system

From the time I purchased this I've had ongoing issues with the java, flash, OS updates causing the computer to hang forever. Sometimes I end up having to press the off button because Command Q and Command/Option/Escape won't allow a force quit even after a 20 minute wait. I don't know enough about what's going on behind the boot up to know what's wrong. Here is a copy of my console log and this is exactly what they look like each time after I have gone in and done a disk verify, (says it's okay) and then repair disk permissions. I've had to boot to safe mode 3 times today and repair permissions due to this issue. There is nothing plugged into the computer except the power cord. The OS is up to date per Software Update and the only 3rd party software installed is SKYPE ...
1/25/11 5:45:58 PM SoftwareUpdateCheck[520] Checking for updates
1/25/11 5:45:58 PM storeagent[524] port created
1/25/11 5:46:27 PM com.apple.launchd[1] (com.apple.suhelperd[522]) Exited with exit code: 2
1/25/11 5:46:27 PM com.apple.launchd.peruser.501[88] ([0x0-0x3d03d].SoftwareUpdateCheck[520]) Exited with exit code: 102
1/25/11 8:21:42 PM [0x0-0x52052].com.skype.skype[613] Main starting with pid 613 parent pid 88
1/25/11 8:21:43 PM Skype[613] SkypeApplication::init called
1/25/11 10:56:56 PM com.apple.launchd[1] * launchd[1] has started up. *
1/25/11 11:09:29 PM com.apple.fontd[70] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
1/25/11 11:09:31 PM com.apple.WindowServer[72] Tue Jan 25 23:09:31 Troy-Lindstroms-MacBook.local WindowServer[72] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
1/25/11 11:09:32 PM com.apple.fontd[70] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
1/25/11 11:09:40 PM com.apple.UserEventAgent-LoginWindow[79] ALF error: cannot find useragent 1102
1/25/11 11:09:40 PM com.apple.UserEventAgent-LoginWindow[79] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
1/25/11 11:09:40 PM com.apple.launchd.peruser.501[90] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
1/25/11 11:09:42 PM fontd[100] Database content version mismatch (stored(15) != expected(14))
1/25/11 11:09:47 PM com.apple.launchd.peruser.501[90] (com.apple.Kerberos.renew.plist[108]) Exited with exit code: 1
1/25/11 11:10:09 PM com.apple.coreservicesd[44] ThrottleProcessIO: throttling disk i/o
1/25/11 11:10:12 PM com.apple.coreservicesd[44] ThrottleProcessIO: throttling disk i/o
1/25/11 11:10:13 PM com.apple.launchd.peruser.501[90] (com.apple.AirPortBaseStationAgent[110]) Exited: Killed
1/25/11 11:10:14 PM com.apple.loginwindow[22] shutdown: / is busy updating; waiting for lock
1/25/11 11:10:33 PM com.apple.launchd[1] * launchd[1] has started up. *
1/25/11 11:11:24 PM com.apple.UserEventAgent-LoginWindow[81] ALF error: cannot find useragent 1102
1/25/11 11:11:24 PM com.apple.UserEventAgent-LoginWindow[81] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
1/25/11 11:11:24 PM com.apple.launchd.peruser.501[90] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
1/25/11 11:11:28 PM fontd[101] Database content version mismatch (stored(15) != expected(14))
1/25/11 11:11:28 PM fontd[101] Failed to open read-only database, regenerating DB
1/25/11 11:11:34 PM com.apple.launchd.peruser.501[90] (com.apple.Kerberos.renew.plist[111]) Exited with exit code: 1
1/25/11 11:11:40 PM com.apple.fontd[101] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
1/25/11 11:11:48 PM com.apple.fontd[101] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
1/25/11 11:11:49 PM [0x0-0x9009].com.skype.skype[116] Main starting with pid 116 parent pid 90
1/25/11 11:11:51 PM Skype[116] SkypeApplication::init called
1/25/11 11:38:12 PM com.apple.WindowServer[69] Tue Jan 25 23:38:12 Troy-Lindstroms-MacBook.local WindowServer[69] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
1/26/11 11:36:13 AM [0x0-0x6d06d].com.skype.skype[666] Main starting with pid 666 parent pid 90
1/26/11 11:36:14 AM Skype[666] SkypeApplication::init called
1/26/11 12:25:04 PM com.apple.launchd.peruser.501[90] ([0x0-0x6d06d].com.skype.skype[666]) Exited: Terminated
1/26/11 5:45:58 PM SoftwareUpdateCheck[867] Checking for updates
1/26/11 5:45:58 PM storeagent[870] port created
1/26/11 5:47:17 PM com.apple.launchd[1] (com.apple.suhelperd[869]) Exited with exit code: 2
1/26/11 5:47:17 PM com.apple.launchd.peruser.501[90] ([0x0-0x92092].SoftwareUpdateCheck[867]) Exited with exit code: 102
1/26/11 8:32:58 PM [0x0-0x11011].com.apple.Safari[143] Wed Jan 26 20:32:58 Troy-Lindstroms-MacBook.local Safari[143] <Error>: unknown error code: invalid drawable
1/26/11 8:32:58 PM [0x0-0x11011].com.apple.Safari[143] Wed Jan 26 20:32:58 Troy-Lindstroms-MacBook.local Safari[143] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
1/26/11 8:33:10 PM [0x0-0x11011].com.apple.Safari[143] Wed Jan 26 20:33:10 Troy-Lindstroms-MacBook.local Safari[143] <Error>: unknown error code: invalid drawable
1/26/11 8:33:24 PM [0x0-0x11011].com.apple.Safari[143] Wed Jan 26 20:33:24 Troy-Lindstroms-MacBook.local Safari[143] <Error>: unknown error code: invalid drawable
1/26/11 10:48:32 PM com.apple.launchd.peruser.501[90] ([0x0-0x11011].com.apple.Safari[143]) Exited: Terminated
1/26/11 10:49:37 PM com.apple.launchd[1] (com.apple.suhelperd[1047]) Exited with exit code: 2
1/26/11 10:49:44 PM com.apple.launchd.peruser.501[90] (com.apple.AirPortBaseStationAgent[113]) Exited: Killed
1/27/11 11:39:52 PM com.apple.launchd[1] * launchd[1] has started up. *
1/27/11 11:40:14 PM com.apple.launchd.peruser.501[84] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
1/27/11 11:40:15 PM com.apple.UserEventAgent-LoginWindow[77] ALF error: cannot find useragent 1102
1/27/11 11:40:15 PM com.apple.UserEventAgent-LoginWindow[77] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
1/27/11 11:40:15 PM SoftwareUpdateCheck[98] Checking for updates
1/27/11 11:40:15 PM com.apple.launchd.peruser.501[84] (com.apple.Kerberos.renew.plist[111]) Exited with exit code: 1
1/27/11 11:40:17 PM storeagent[119] port created
1/27/11 11:40:21 PM com.apple.WindowServer[65] Thu Jan 27 23:40:21 Troy-Lindstroms-MacBook.local WindowServer[65] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
1/27/11 11:40:27 PM [0x0-0xa00a].com.skype.skype[116] Main starting with pid 116 parent pid 84
1/27/11 11:40:29 PM Skype[116] SkypeApplication::init called
1/27/11 11:41:02 PM SoftwareUpdateCheck[98] Downloading "iTunes"
1/27/11 11:42:35 PM SoftwareUpdateCheck[98] Auto-download of "iTunes" SUCCESSFUL.
1/27/11 11:42:35 PM SoftwareUpdateCheck[98] Launching app
1/27/11 11:43:20 PM com.apple.launchd.peruser.501[84] ([0x0-0x6006].SoftwareUpdateCheck[98]) Exited with exit code: 102
1/28/11 9:51:59 AM com.apple.RemoteUI[589] CoreAnimation: rendering error 501
1/28/11 9:52:15 AM com.apple.RemoteUI[589] HTTP2 Streaming Reads ON
1/28/11 11:31:15 AM com.apple.launchd.peruser.501[84] ([0x0-0x10010].com.apple.Safari[134]) Exited: Terminated
1/28/11 11:42:21 AM com.apple.launchd[1] (com.apple.suhelperd[104]) Exited with exit code: 2
1/28/11 3:49:50 PM com.apple.launchd.peruser.501[84] (com.apple.AirPortBaseStationAgent[113]) Exited: Killed
1/28/11 3:49:50 PM com.apple.launchd.peruser.501[84] ([0x0-0x80080].com.apple.iTunesHelper[764]) Exited: Killed
1/28/11 3:50:10 PM com.apple.launchd.peruser.501[84] (com.apple.Dock.agent[88]) Exit timeout elapsed (20 seconds). Killing
1/28/11 3:53:36 PM com.apple.launchd[1] * launchd[1] has started up. *
1/28/11 3:55:16 PM com.apple.launchd.peruser.501[90] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
1/28/11 3:55:16 PM com.apple.UserEventAgent-LoginWindow[82] ALF error: cannot find useragent 1102
1/28/11 3:55:16 PM com.apple.UserEventAgent-LoginWindow[82] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
1/28/11 3:55:25 PM com.apple.launchd.peruser.501[90] (com.apple.Kerberos.renew.plist[111]) Exited with exit code: 1
1/28/11 3:55:27 PM com.apple.WindowServer[72] Fri Jan 28 15:55:27 Troy-Lindstroms-MacBook.local WindowServer[72] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
1/28/11 3:55:40 PM [0x0-0x8008].com.skype.skype[115] Main starting with pid 115 parent pid 90
1/28/11 3:55:41 PM Skype[115] SkypeApplication::init called
1/28/11 11:40:16 PM SoftwareUpdateCheck[419] Checking for updates
1/28/11 11:40:16 PM storeagent[422] port created
1/28/11 11:40:59 PM com.apple.launchd[1] (com.apple.suhelperd[421]) Exited with exit code: 2
1/28/11 11:40:59 PM com.apple.launchd.peruser.501[90] ([0x0-0x56056].SoftwareUpdateCheck[419]) Exited with exit code: 102
1/29/11 3:02:24 AM quicklookd[551] [QL] 'Creating thumbnail' timed out for '<QLThumbnailRequest /Users/troylindstrom/Downloads/images-30.jpeg>' (Start date: 2011-01-29 03:02:04 -0800)
1/29/11 3:05:11 AM quicklookd[555] [QL] 'Creating thumbnail - cancelled' timed out for '<QLThumbnailRequest /Users/troylindstrom/Downloads/About Downloads.pdf>' (Start date: 2011-01-29 03:03:35 -0800)
1/29/11 3:05:52 AM quicklookd[560] [QL] 'Creating thumbnail' timed out for '<QLThumbnailRequest /Users/troylindstrom/Downloads/About Downloads.pdf>' (Start date: 2011-01-29 03:05:32 -0800)
1/29/11 3:06:44 AM quicklookd[563] [QL] 'Creating thumbnail' timed out for '<QLThumbnailRequest /Users/troylindstrom/Downloads/images-3.jpeg>' (Start date: 2011-01-29 03:06:22 -0800)
1/29/11 6:37:03 AM com.apple.launchd.peruser.501[90] ([0x0-0x86086].com.apple.Preview[708]) Exited: Killed
1/29/11 6:37:03 AM com.apple.launchd.peruser.501[90] ([0x0-0x8a08a].com.apple.systemevents[721]) Exited: Killed
1/29/11 6:37:03 AM com.apple.launchd.peruser.501[90] (com.apple.AirPortBaseStationAgent[113]) Exited: Killed
1/29/11 6:37:13 AM com.apple.launchd[1] * launchd[1] has started up. *
1/29/11 6:37:42 AM com.apple.UserEventAgent-LoginWindow[81] ALF error: cannot find useragent 1102
1/29/11 6:37:42 AM com.apple.UserEventAgent-LoginWindow[81] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
1/29/11 6:37:42 AM com.apple.launchd.peruser.501[89] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
1/29/11 6:37:50 AM com.apple.WindowServer[54] Sat Jan 29 06:37:50 Troy-Lindstroms-MacBook.local WindowServer[54] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
1/29/11 6:37:52 AM com.apple.launchd.peruser.501[89] (com.apple.Kerberos.renew.plist[109]) Exited with exit code: 1
1/29/11 6:38:03 AM [0x0-0x8008].com.skype.skype[113] Main starting with pid 113 parent pid 89
1/29/11 6:38:05 AM Skype[113] SkypeApplication::init called
1/29/11 12:14:57 PM [0x0-0x36036].com.apple.CharacterPaletteIM[330] objc[330]: Class ThinDividerSplitView is implemented in both /System/Library/Input Methods/CharacterPalette.app/Contents/MacOS/CharacterPalette and /System/Library/Input Methods/CharacterPalette.app/Contents/PlugIns/RomanView.CharPalettePlugin/Conte nts/MacOS/RomanView. One of the two will be used. Which one is undefined.
1/29/11 12:43:40 PM [0x0-0x39039].com.apple.CharacterPaletteIM[346] objc[346]: Class ThinDividerSplitView is implemented in both /System/Library/Input Methods/CharacterPalette.app/Contents/MacOS/CharacterPalette and /System/Library/Input Methods/CharacterPalette.app/Contents/PlugIns/RomanView.CharPalettePlugin/Conte nts/MacOS/RomanView. One of the two will be used. Which one is undefined.
1/29/11 6:52:46 PM com.apple.launchd.peruser.501[89] ([0x0-0xf00f].com.apple.Safari[131]) Exited: Terminated
1/29/11 6:52:59 PM com.apple.launchd.peruser.501[89] ([0x0-0x1e01e].com.apple.AddressBook[206]) Exited: Terminated
1/29/11 6:52:59 PM loginwindow[29] * -[NSCFArray objectAtIndex:]: index (1) beyond bounds (1)
1/29/11 6:52:59 PM com.apple.loginwindow[29] 2011-01-29 18:52:59.446 loginwindow[29:107] * -[NSCFArray objectAtIndex:]: index (1) beyond bounds (1)
1/29/11 6:53:14 PM com.apple.launchd.peruser.501[89] (com.apple.AirPortBaseStationAgent[111]) Exited: Killed
1/30/11 9:17:52 AM com.apple.launchd[1] * launchd[1] has started up. *
1/30/11 9:19:51 AM com.apple.fontd[66] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
1/30/11 9:19:51 AM com.apple.WindowServer[68] Sun Jan 30 09:19:51 Troy-Lindstroms-MacBook.local WindowServer[68] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
1/30/11 9:19:54 AM com.apple.fontd[66] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
1/30/11 9:20:00 AM com.apple.UserEventAgent-LoginWindow[78] ALF error: cannot find useragent 1102
1/30/11 9:20:00 AM com.apple.UserEventAgent-LoginWindow[78] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
1/30/11 9:20:00 AM com.apple.launchd.peruser.501[86] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
1/30/11 9:20:02 AM fontd[98] Database content version mismatch (stored(15) != expected(14))
1/30/11 9:20:04 AM SoftwareUpdateCheck[94] Checking for updates
1/30/11 9:20:05 AM storeagent[102] port created
1/30/11 9:20:08 AM com.apple.launchd.peruser.501[86] (com.apple.Kerberos.renew.plist[109]) Exited with exit code: 1
1/30/11 9:20:38 AM com.apple.launchd.peruser.501[86] (com.apple.AirPortBaseStationAgent[111]) Exited: Killed
1/30/11 9:20:39 AM com.apple.loginwindow[22] shutdown: / is busy updating; waiting for lock
1/30/11 9:20:44 AM com.apple.launchd[1] (com.apple.suhelperd[101]) Exited with exit code: 2
1/30/11 9:20:45 AM com.apple.launchd.peruser.501[86] ([0x0-0x6006].SoftwareUpdateCheck[94]) Exited with exit code: 102
1/30/11 9:20:49 AM com.apple.coreservicesd[44] ThrottleProcessIO: throttling disk i/o
1/30/11 9:20:55 AM com.apple.coreservicesd[44] ThrottleProcessIO: throttling disk i/o
1/30/11 9:21:16 AM com.apple.launchd[1] * launchd[1] has started up. *
1/30/11 9:22:04 AM com.apple.UserEventAgent-LoginWindow[81] ALF error: cannot find useragent 1102
1/30/11 9:22:04 AM com.apple.UserEventAgent-LoginWindow[81] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
1/30/11 9:22:04 AM com.apple.launchd.peruser.501[89] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
1/30/11 9:22:07 AM fontd[101] Database content version mismatch (stored(15) != expected(14))
1/30/11 9:22:07 AM fontd[101] Failed to open read-only database, regenerating DB
1/30/11 9:22:11 AM com.apple.fontd[101] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
1/30/11 9:22:13 AM com.apple.launchd.peruser.501[89] (com.apple.Kerberos.renew.plist[111]) Exited with exit code: 1
1/30/11 9:22:19 AM com.apple.WindowServer[69] Sun Jan 30 09:22:19 Troy-Lindstroms-MacBook.local WindowServer[69] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
1/30/11 9:22:26 AM com.apple.fontd[101] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
1/30/11 9:22:26 AM [0x0-0x9009].com.skype.skype[116] Main starting with pid 116 parent pid 89
1/30/11 9:22:28 AM Skype[116] SkypeApplication::init called
1/30/11 10:33:53 AM com.apple.launchd.peruser.501[89] (com.apple.AirPortBaseStationAgent[113]) Exited: Killed
1/30/11 10:34:02 AM com.apple.launchd[1] * launchd[1] has started up. *
1/30/11 10:34:26 AM com.apple.launchd.peruser.501[86] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
1/30/11 10:34:26 AM com.apple.UserEventAgent-LoginWindow[79] ALF error: cannot find useragent 1102
1/30/11 10:34:26 AM com.apple.UserEventAgent-LoginWindow[79] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
1/30/11 10:34:28 AM com.apple.launchd.peruser.501[86] (com.apple.Kerberos.renew.plist[107]) Exited with exit code: 1
1/30/11 10:34:32 AM [0x0-0x8008].com.skype.skype[112] Main starting with pid 112 parent pid 86
1/30/11 10:34:36 AM Skype[112] SkypeApplication::init called
1/30/11 3:37:45 PM com.apple.launchd[1] * launchd[1] has started up. *
1/30/11 3:50:19 PM com.apple.fontd[68] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
1/30/11 3:50:19 PM com.apple.WindowServer[69] Sun Jan 30 15:50:19 Troy-Lindstroms-MacBook.local WindowServer[69] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
1/30/11 3:50:21 PM com.apple.fontd[68] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
1/30/11 3:50:52 PM com.apple.coreservicesd[45] ThrottleProcessIO: throttling disk i/o
1/30/11 3:53:14 PM com.apple.UserEventAgent-LoginWindow[80] ALF error: cannot find useragent 1102
1/30/11 3:53:14 PM com.apple.UserEventAgent-LoginWindow[80] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
1/30/11 3:53:14 PM com.apple.launchd.peruser.501[90] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
1/30/11 3:53:15 PM fontd[101] Database content version mismatch (stored(15) != expected(14))
1/30/11 3:53:18 PM com.apple.coreservicesd[45] ThrottleProcessIO: throttling disk i/o
1/30/11 3:53:20 PM com.apple.launchd.peruser.501[90] (com.apple.Kerberos.renew.plist[109]) Exited with exit code: 1
1/30/11 4:00:53 PM com.apple.launchd.peruser.501[90] (com.apple.AirPortBaseStationAgent[111]) Exited: Killed
1/30/11 4:12:07 PM com.apple.launchd[1] * launchd[1] has started up. *
1/30/11 4:12:56 PM com.apple.UserEventAgent-LoginWindow[81] ALF error: cannot find useragent 1102
1/30/11 4:12:56 PM com.apple.UserEventAgent-LoginWindow[81] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
1/30/11 4:12:56 PM com.apple.launchd.peruser.501[89] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
1/30/11 4:12:59 PM fontd[101] Database content version mismatch (stored(15) != expected(14))
1/30/11 4:12:59 PM fontd[101] Failed to open read-only database, regenerating DB
1/30/11 4:13:06 PM com.apple.launchd.peruser.501[89] (com.apple.Kerberos.renew.plist[111]) Exited with exit code: 1
1/30/11 4:13:15 PM com.apple.fontd[101] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
1/30/11 4:13:21 PM com.apple.fontd[101] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
1/30/11 4:13:21 PM [0x0-0x9009].com.skype.skype[116] Main starting with pid 116 parent pid 89
1/30/11 4:13:23 PM Skype[116] SkypeApplication::init called
1/30/11 5:12:33 PM com.apple.WindowServer[69] Sun Jan 30 17:12:33 Troy-Lindstroms-MacBook.local WindowServer[69] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
1/30/11 5:12:34 PM com.apple.RemoteUI[169] CoreAnimation: rendering error 501
1/30/11 5:12:46 PM com.apple.launchd.peruser.501[89] ([0x0-0x9009].com.skype.skype[116]) Exited: Terminated
1/30/11 5:12:49 PM com.apple.RemoteUI[169] HTTP2 Streaming Reads ON
1/30/11 5:13:12 PM System Preferences[175] .scriptSuite warning for result type of command 'timedLoad' in suite 'SystemPreferences': the type NSNumber ('long') doesn't match the result Apple event code ('doub').
1/31/11 12:17:59 AM com.apple.launchd[1] (com.apple.aslmanager) Throttling respawn: Will start in 5 seconds
1/31/11 12:54:05 AM com.apple.launchd.peruser.501[89] ([0x0-0x18018].com.apple.Safari[180]) Exited: Terminated
1/31/11 1:31:00 AM com.apple.launchd.peruser.501[89] (com.apple.AirPortBaseStationAgent[113]) Exited: Killed
1/31/11 1:31:24 AM com.apple.launchd[1] * launchd[1] has started up. *
1/31/11 1:33:28 AM com.apple.fontd[66] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
1/31/11 1:33:29 AM com.apple.WindowServer[67] Mon Jan 31 01:33:29 Troy-Lindstroms-MacBook.local WindowServer[67] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
1/31/11 1:33:31 AM com.apple.fontd[66] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
1/31/11 1:33:48 AM com.apple.UserEventAgent-LoginWindow[76] ALF error: cannot find useragent 1102
1/31/11 1:33:48 AM com.apple.UserEventAgent-LoginWindow[76] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
1/31/11 1:33:48 AM com.apple.launchd.peruser.501[86] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
1/31/11 1:33:50 AM fontd[96] Database content version mismatch (stored(15) != expected(14))
1/31/11 1:33:54 AM com.apple.launchd.peruser.501[86] (com.apple.Kerberos.renew.plist[105]) Exited with exit code: 1
1/31/11 1:34:13 AM com.apple.coreservicesd[44] ThrottleProcessIO: throttling disk i/o
1/31/11 1:34:13 AM com.apple.coreservicesd[44] ThrottleProcessIO: throttling disk i/o
1/31/11 1:44:00 AM com.apple.launchd.peruser.501[86] (com.apple.AirPortBaseStationAgent[107]) Exited: Killed
1/31/11 1:44:10 AM com.apple.launchd[1] * launchd[1] has started up. *
1/31/11 1:44:43 AM com.apple.launchd.peruser.501[86] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
1/31/11 1:44:43 AM fontd[95] Database content version mismatch (stored(15) != expected(14))
1/31/11 1:44:43 AM fontd[95] Failed to open read-only database, regenerating DB
1/31/11 1:44:44 AM com.apple.UserEventAgent-LoginWindow[79] ALF error: cannot find useragent 1102
1/31/11 1:44:44 AM com.apple.UserEventAgent-LoginWindow[79] plugin.UserEventAgentFactory: called with typeID=FC86416D-6164-2070-726F-70735C216EC0
1/31/11 1:44:45 AM com.apple.launchd.peruser.501[86] (com.apple.Kerberos.renew.plist[108]) Exited with exit code: 1
1/31/11 1:44:45 AM com.apple.fontd[95] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
1/31/11 1:44:57 AM com.apple.fontd[95] FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
1/31/11 1:44:58 AM [0x0-0x8008].com.skype.skype[112] Main starting with pid 112 parent pid 86
1/31/11 1:45:00 AM Skype[112] SkypeApplication::init called
1/31/11 2:00:28 AM com.apple.launchd[1] (com.apple.suhelperd[141]) Exited with exit code: 2
Can anyone see the issue or tell me what I need to do to fix this thing???

Which MacBook model? Did it come with OSX 10.6 or did you upgrade it?

Need advice on Repairing Disk Permissions...

I need some input from those who know how to Repair Disk Permissions (under Disk Utility, for those who don't know).
Basically, I lost a TON of my Access and Privileges on my G4 recently--which I really only noticed after iTunes would no longer let me import anything (no matter how many times I tried changing the Ownership & Permissions on my Music folder's Info section)--which, I might add, I suffered due to a virus caused by Limewire. As had been suggested to me, I Verified Disk Permissions, and saw that I had a TON of problems listed on my startup HD. So I'm now seeking ways to repair them.
Now, the most obvious way is using the Repair Disk Permissions program (which I've actually never had to use before). However, under OS10.3.9, when I select the Repair Disk Permissions on Disk Utility, in listing all my Drives available, it actually shows the drive in 2 formats/pictures:
1) the actual technical name/manufactor model/GB size of the drive (on top), and
2) the Desktop name and Icon picture of the Drive as it appears on my desktop.
This confuses me: as you can guess, the startup Drive in question is only partioned as one. So on Disk Utility, which of these 2 pictured drives do I have to highlight and Repair Disk Permissions to (i.e. 19GB Maxtor32049 Vs. 'HAL')?
Also, for those of you who have used other means (programs) to change Disk Permissions, which would you recommend? For example, I got a program from Versiontracker called BatCHmod, but I don't know if something like it is any safer than just using Repair Disk Permissions. Because unfortunately, I'm running out of room on my disk, and don't have nearly enough space on my other drive to hope to back the whole Drive up to.
Please help!!!

Hi phasmatrope!
TO REPAIR PERMISSIONS ON THE STARTUP DISK
1.Open Disk Utility, located in Applications/Utilities, and select the startup disk HAL, in the left column.
2.Click First Aid.
3.Click Verify Disk Permissions to test permissions or Repair Disk Permissions to test and repair permissions. (I never "Verify". Just run "Repair".)
Rerun RP until the only message it reports is:
"We are using special permissions for the file or directory ./System/Library/Filesystems/cd9660.fs/cd9660.util.
New permissions are 33261"
This is a status message and not a cause for concern. You may safely ignore it.
Or these:
"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"
Again, these are status messages, which appeared after Security Update 2005-001.
There may be others that you can ignore. Complete lists at link below.
Spurious Permissions Errors In 10.3.x
When "Repair Permissions" is complete. Quit "Disk Utility".
Good Luck!
ali b

Apple: Repair "Repair Disk Permissions"

The Leopard version of Repair Disk Permissions is broke. No matter what it is doing behind the screen, it comes up with the chirpy "Repairing Disk Permissions. Estimated time: Less than 1 minute" then proceeds to wait five minutes (on a 160 GB MacBook Pro of recent vintage) before starting to move the bar from its initial, deceptive, 20% fulfilled position.
This performance and feedback flies in the face of Apple's own software behavioral edicts.
After the five-minute wait, it takes an additional 4:30 to move the bar to the end, even when it's the second run on the same drive. The reported times are NEVER accurate, never even approximate until the last 50 seconds.
And don't even get me started with all the reported failures to fix anything that consistently show up every single time.
In five minutes (300 seconds) my computer has the ability to impose 4.4 Billion computational cycles on the task of sorting out whatever ails my hard disk--per second. That's just a TRILLION point three total mathematical operations that might be brought to bear on thinking about what to do before starting to access the disk and fix its errant map of data.
To give that some scale, at one second per math problem, that equals around 42 thousand years. Which ought to be time enough to evolve the program into a more advanced version...
Message was edited by: Peter Inova1
Message was edited by: Peter Inova1
Message was edited by: Peter Inova1
Message was edited by: Peter Inova1

It's an interesting but irrelevant observation.
Disk Repair is not a mathematical operation - it obviously involves many disk reads - often the slowest component on a computer in terms of access times. Should any repairs be required - the system will then write and likely re-read to ensure the write was successful.
You are trying to figure out future events - how long the next action will take based on prior events - sometimes things change that make past performance a poor estimate of future performance.
As for estimating times - I've programmed this - and observed many attempts to do so - few work well or offer estimates anywhere near accurate. Observe the estimated times to complete a download in iTunes or the time to copy a file. I have seen many cases where the estimates said "10 seconds" and I waited minutes for them to complete.

Rationale for Repairing Disk Permissions

I repair permissions before and after installations, and I suggest others to do so. However, I have read in some threads in Discussions there there is no technical basis for repairing disk permissions before installation, and that only repairing after installation is necessary.
I realize that there are different opinions about this, but beyond opinions is there a technical basis or rationale for repairing disk permissions before installations?
Thanks.
cornelius
Message was edited by: cornelius

Hi cornelius,
Here is some reading about this topic. Mind that Apple DOES recommend repairing permissions as routine maintenance (see links at the bottom)! My suggestion to Repair permissions before and after an update has a very simple rational: If you forgot to repair permissions AFTER the last update you might get into trouble. Therefore it is safe and costs only a few seconds to do it before and after the update.
mac.column.ted: Unravelling the Repair Disk Permissions controversy
"Ted Landau
May 2006
Repairing Disk Permissions. Not exactly a topic that you would expect to spark much controversy. Yet, surprisingly, it is the focal point of a rather heated debate.
The command itself is innocuous enough. It is included as part of the First Aid component of Disk Utility. Apple's Help for Disk Utility states: "User permissions associated with files, folders, or applications can become damaged and prevent a file or application from opening. Permissions problems can also cause your computer to run slowly. Using Disk Utility, you may be able to fix these permissions problems...Repairing permissions may also be recommended after updating the system or installing new software."
Consistent with this, many users and Web sites (including MacFixIt and at least some postings on MacinTouch) recommend the use of Repair Disk Permissions, not only for specific signs of trouble, but as a part of generic troubleshooting and ongoing maintenance for your Mac.
In contrast, other members of the Mac community (writing in locations such as the Daring Fireball , Unsanity, and the MDJ) argue that running this command just for maintenance, in the absence of any particular symptom, is essentially worthless. Some critics go even further and claim there is no justification for ever selecting to repair permissions. Not only is it useless, they contend, but it may even cause new problems to appear. This viewpoint is often expressed with inflammatory rhetoric such as "covering yourself in Vaseline and rolling around naked in the dirt and repairing permissions are just as likely to fix your Mac OS X problem" (Unsanity).
Regardless of who's right or wrong, I don't believe that insulting users is merited here, especially when these users are simply following advice suggested by Apple itself. As it turns out, I also do not agree with the position of these critics. So, although I may be stepping into a minefield, here's my own take on this subject and my resulting recommendations. [Disclaimer: I was not involved in the authorship of previous MacFixIt articles on this subject. This column is my separate opinion, and does not necessarily reflect the views of MacFixIt.]: Continued"
Mac OS X 10.3 Help: "It's a good idea to repair disk permissions as a regular maintenance task after upgrading or installing new software."
Mac OS X 10.4 Help: "It's a good idea to repair disk permissions as a regular maintenance task after upgrading or installing new software."
Randy B. Singer: Macintosh OS X Routine Maintenance

Constantly repairing disk permissions for Spotlight to work

I am constantly having to use Disk Utility and repair my disk permissions in order to get Spotlight to work. Often I'll type something such as an application and the only thing that will show up is the Definition from the dictionary.
Repairing the disk permissions seems to fix the problem, but it doesn't take long before I need to once again go in and repair in order to get Spotlight working again. I've tried dragging the whole hard drive into the exclusions list and then removing it again so the index will rebuild. That also works but again only lasts a short time.
Any help would be much appreciated!

whiskey sour wrote:
I hear a lot about 'defraggin' in Windows. Is there something similar in Mac, ie: is Repairing Disk Permissions something similar?
They're entirely different things. A "defragment" operation moves files around to combine split segments of files and consolidate free space. A "repair permissions" operation examines the permissions settings of system files and resets any that seem to be wrong.
Here's what Apple has to say about defragmenting a Mac disk:
http://support.apple.com/kb/HT1634

Verifying/Repairing Disk Permissions

I have read in the Forum that one should run Disk Permissions before and after updates, and it doesn't hurt to run it once in a while anyway. But it isn't clear to me when one should verify and when one should repair. After verification, we get the message "Permissions verification complete. Privileges have been verified OR REPAIRED" (capitalization mine). If the verification takes care of repairs, when should one click on the "Repair Disk Permissions"? Thanks.

There's no point in verifying. Always repair. However, repairing permissions need only be done before installing new system updates or after installing third-party software that uses a proprietary installer.
Before installing system updates I recommend doing this:
Repairing the Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger and Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior (4.0 for Tiger, and 4.1 for Leopard) and/or TechTool Pro (4.6.1 for Leopard) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.

Problem repairing disk permissions

Hey all, I'm trying to help a friend with a sick macbook I think it's a pro, but I definitely know he's running OS 10.5.
I tried to repair his disk permissions in the Disk Utility, and I keep getting the same three messages- "ACL found but not expected in system folder", "ACL found but not expected in Library", and the same thing in one other folder which I forget right now....
I ran the "repair disk permissions" operation three times in a row and keep getting the same three messages. Each running takes about ten minutes and the progress bar hangs at about 15% completion for 90% of the operation. Then in the last minute, it charges across the screen, the operation completes and those messages pop up.
I've never had anything like this happen (when repeated attempts at repairing seemingly don't accomplish the repair of permissions).
Any advice? No other repairs are being logged.

Leopard 10.5 has Access Control Lists enabled and uses them for some of the system folders. The Disk Utility is just informing you that an Access Control List was found, but the information used to repair the permissions doesn't show one. Probably what happened is the "apply to enclosed items" was used from the Get Info window, which added ACLs to the enclosed items. The Get Info window doesn't show extended permissions very well, so applying the permissions to enclosed items shouldn't be used on system files and folders.

Cannot, View or Repair Disk Permissions with disk utility,

Hey,
I can't repair disk permissions using Disk Utility.
I can only repair them using the boot disk and I'm just worried that something somewhere is corrupted or gone irky (Technical computer term).
Thanks.

Installed Lion on my 27" iMac (mid 2010) and everyday since it shuts down after start up.
Called Apple they said repair permissions, after safe boot. Thats works but only for the next restart.
When I shutdown and start up the next day I have to go thru the same process.
Anybody else have this problem?

CD Ejects with Error Code 9 - Repair Disk Permissions Greyed Out

History:
Superdrive 815CA Ejects Blank CD's to be burned w/ Error Code 9
Exact Text:
The Operation Could not be completed an unexpected error occured(error Code 9)
The CD Ejects, but the Ghost Icon of the CD image would stay
Plays previously burnt CD's/DVD's as well as market CD's/DVD's fine
Went to Disk Utility
Repair Disk Permissions(RDP) & Verify Disk Permissions(VDP) greyed out so you can'tclick them when I click on first aid
The only time they weren't greyed was when I clicked to repair the Ghost Icon CD, of which the actual CD was ejected in the first place
I cleaned the lens umteen million times - same problem
I did the Hardware repair check w/the startup CD, same problem
I bought a NEW frickin' Superdrive and installed it successfully- same problem
I went to system preferences and selected the option to open the blank CD in I tunes.
This worked for burning MP3's no problem
HOWEVER it will not open in the finder, so I can't save any data from my desktop on to a CD/DVD, so my hard Drive is getting clogged
Got a Hammer?

I loaded at least 20 different BLANK CD's to experiment with.
The same CD's which get spat out when I open it in finder, burn fine when i open them up in I tunes
I've already bought a new drive and the same problem occurs as when i had the old drive (can't open in finder), so i believe the bad drive and bad CD premise has been troubleshot.
It seems like it won't recognize the Drive or CD when i try to launch a CD from the finder
The blank CD's burn music fine when I open it up in I tunes, but not when I try to open it up in the finder when i try to put data on the CD's.

Repair Disk Permissions: is it a safe operation ?

Similar Messages

Maybe you are looking for