Repair disk permissions "greyed out"

We have a G5 with 2 internal hard drives that we use as a server. I can run "repair disk permissions" on one drive, but on the other the choices for repair or verify disk permissions is greyed out. Why is this and how can I repair the permissions on the one drive?

2 possibilities come to mind.
(1) The disk in question does not have Mac OS X installed on it (required for permission repair).
(2) The disk in question does not have suitable files in the /Library/Receipts folder (such a folder doesn't exist, I guess, if OS X isn't there - see (1)).
charlie

Similar Messages

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 grayed out

Hello,
I have a WD External Drive that I use for Time Machine backup. Recently have had no backup (about 20 days) and finally decided to look into it. I use this one at work and have brought it home to work on what is wrong. Have tried to repair disk permissions, but option is grayed out. I have however been able to repair disk. It took 8 hours to repair disk which reported no problems.
I have tried to copy files from the backup disk to another disk, but it won't work (don't remember exact message-but it was something odd).
From another thread, I was trying to do this command:
sudo /usr/sbin/chown _installer:admin /Library/Receipts/db/a.receiptdb
and got this response:
Home-Power-Mac-G5:~ paul$ sudo /usr/sbin/chown _installer:admin /Library/Receipts/db/a.receiptdb
Password:
paul is not in the sudoers file. This incident will be reported.
so, I then try this command:
ls -leO /Library/Receipts/db/a.receiptdb
and get this response:
-rw------- 1 _installer wheel - 266133504 Dec 15 22:03 /Library/Receipts/db/a.receiptdb
WHAT do I do now? I want to first back up all files then reformat drive to start anew.

Hi Christopher Graham;
Since Repair Permission is repair the permissions for the system there has to be a system on the partition in order to not have that button ghosted. As far as Disk Utility can tell a Time Machine backup is not a System hence it is ghosted.
Allan

REPAIR DISK button greyed out

I wanted to VERIFY a volume and received and red-letter error that the volume needed repair.
Here is the exact message:
Verifying volume “Macintosh HD”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Invalid node structure
The volume Macintosh HD needs to be repaired.
Error: The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
However, the REPAIR DISK button is greyed out. How can I repair this VOLUME if there is no REPAIR option?
Thanks,
Joel DuBay
Bass Traps and Acoustic Panels
http://www.readyacoustics.com

Joel,
You are probably going to find that booting to the install disk and running Disk Utility that way isn't going to help any further that "fsck" did. In fact, there is no difference between the command line "fsck" and Disk Utility's "Repair Disk" routine.
What you have is a disk error that Disk Utility cannot fix. In most cases, Disk Utility will tell you that it cannot repair a particular error, if such is the case. In rare cases (lke yours), however, Disk Utility or fsck will report that repairs were made, when in fact they were not. I recommend that you do go ahead and make the attempt, but I am betting that you find the error still exists.
Disk Warrior may have better success in making the repair, if you want to pay for it.
However, you should be aware that files are likely to have been damaged by the disk error, and even a successful repair of the file system cannot replace any data that has been lost. In other words, any critical system files that are currently damaged will remain so, and any problems you are experiencing as a result of the damaged files will still exist.
Unfortunately, the only way to fix these damaged files is to format and reinstall, preferably "zeroing" the drive in the process. Since this necessitates making a good backup first, that should be your biggest concern right now.
If you know how to go about making a comprehensive backup, and are able to do so now, that is what I recommend you do. If you have difficulty making a backup as a result of the disk error, Disk Warrior may be able to help, and it might be worth laying out the cash for it. If, however, you have no problems making a backup, Disk Warrior (and its cost) would be uneccessary, IMO.
Scott

Lion "Verify Disk Permissions" and "Repair Disk Permissions" grayed out

Please help!

Repair using Disk Utility was OK on the volumes, but Repair for the drive was grayed out.
That's very odd. Is your drive G.U.I.D?
Boot into Safe Mode (Hold Shift-Key), then boot normally.

I recently repaired disk permissions on my mac HD and now my on-board speakers wont work, the icon is greyed out and only works when my headphones are plugged in.

I recently repaired disk permissions on my mac HD and now my on-board speakers wont work, the icon is greyed out and only works when my headphones are plugged in

Try to put your headphones several times in and out from your connection, might be the switch is stuck. Normally it should work again while trying to plug the headphones in and out!

Can't repair disk permissions

I just bought a new Mac Mini (2.0 GHz Core Duo w/2 GB of RAM and 320 GB HD) and migrated all of my files over to it from my Time Machine Backup. Over the past two days my two external hard drives have developed permission problems. Yesterday, I booted my computer and my Time Machine backup drive (Western Digital 1 GB) had a small lock on the desktop icon and my permissions were all messed up. I had two versions of my account with "custom" permissions and "Staff" and "Everyone" also with "custom" permissions. I couldn't fix it, so I formatted the drive and now it is working.
Today my other external drive (don't remember maker, 500GB) is doing the same thing (lock on icon, et al), but I don't want to erase it. I tried going to Disk Utility and the verify and repair disk permissions buttons are greyed out. Now, I can't get to my iTunes content on that drive.
Any help would be appreciated.
Thanks,
- Paul

Called Apple Support three times with less than lousy results. My Mac Mini crashed on my first call and it took three Leopard installs before I got back to where I was to begin with.
However, none of the technicians would touch Terminal to fix this issue, but I had found instructions all over the Web. So, I ran some of the commands in Terminal and magically I could fix my permissions on the external HD. I am now repairing permissions on my Macintosh HD and hopefully that will be the end of it.
Phew!

OS won't start up. Repair Disk Permissions moving at snail's pace

After installing a large program (World of Warcraft), my MBP seemed to slow down with frequent beach balls popping up. I decided to restart the system, but now it can't get passed the grey Apple screen. A spinning gear appears on that screen, but nothing else.
The Mac boots fine using a separate firewire drive, so I thought I'd try repairing disk permissions on the MBP drive. Unfortunately, the progress bar in the disk utility fills to about a tenth of the way, and then stops. No error message or anything, just no progression.
Any thoughts?

1. Insert the Mac OS X Install disc that came with your computer, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
3. Click the Erase tab.
4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
5. Select your Mac OS X volume, then chose MacOS Extended Journalled.
6. Click Erase & look for Options. choose Zero 1 pass. This is the option that may mark out the bad blocks.
It still may mean your HDD is going out & may not last though.

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?

Repair Disk Permissions Issues

I'm not sure I am posting this in the correct community but here goes . . .
I have a 17" Macbook Pro running the latest version of Snow Leopard. It is almost 2 years old and I have 4 gb RAM.
Recently, it seems to be slowing down and I have to run repair disk permissions 2-3 times a week to recoup a little speed. I also delete my Firefox cache regularly to try to gain a little there. I do make a few videos in iMovie and initially I thought that was the problem but this week I have not really worked in iMovie much and it is still slow. There seems to be some issues in the log of the repair permissions. I hope they show in this image. I don't know what these mean or how to fix them. It is the "permissions differ" entries I am confused about.

You can ignore those permissions per support article
http://support.apple.com/kb/TA21090
Since you brought up iMove, I suspect your storage is nearly full as this most certainly causes the computer to slow down. video files are the biggest culprit.
Look in your Activity Monitor and reduce the drive space by copying to a external, Disk Utility HFS+ formatted external powered drive of unnecessary files so your boot drive is ideally below 50% filled (yea I know but the computer slows down after that) and not more than 75% filled.
Once you have done that. Get another newer external powered HFS drive and download the free Carbon Copy Cloner and clone the internal drive to the external.
Hold option and boot off the external clone, test it out then use Disk Utility to erase the internal and then reverse clone the external onto the internal, this will defragment and optimize your drive so the OS and programs are on the fast part of the drive, not the slow parts.
Reboot into the internal and run off of the free OnyX's maintainence and cleaning aspects and reboot.
http://www.titanium.free.fr/
Sir speedy machine here we come!
Now of course you may have other issues that could be causing your slow down, like not enough RAM or some sort of failed process or leftover program, tweaks or simply a slow Internet.
You can opt to simply reinstall OS X 10.6 ( by holding c and booting off the installer disk ) over your installed version (doesn't touch files or programs) then immediatly Software Updating until clear, that will clean anything hanging out in OS X.
If you still have slowdowns, then it's in what geeks call "User land" basically something installed outside of root, like a program or only runs in user, not in OS X.
For that you need to create a new user, transfer your files via the Shared Drop and wean yourself off the old user and finally delete it. Also install all new versions of your third party programs removing the originals first.
That should do 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

When I repair disk permissions I get the following:Repairing permissions for "MacIntosh HD" Determining correct file permissions. Permissions differ on ./Library/Widgets, should be drwxr-xr-x , they are drwxrwxr-x Owner and group corrected on ./Library/W

Repairing permissions for “MacIntosh HD”
Determining correct file permissions.
Permissions differ on ./Library/Widgets, should be drwxr-xr-x , they are drwxrwxr-x
Owner and group corrected on ./Library/Widgets
Permissions corrected on ./Library/Widgets
Permissions differ on ./System/Library/User Template, should be drwx------ , they are drwxr-xr-x
Owner and group corrected on ./System/Library/User Template
Permissions corrected on ./System/Library/User Template
Group differs on ./usr/bin/fetchmail, should be 0, group is 6
Permissions differ on ./usr/bin/fetchmail, should be -rwxr-xr-x , they are -rwxr-sr-x
Owner and group corrected on ./usr/bin/fetchmail
Permissions corrected on ./usr/bin/fetchmail
Permissions differ on ./usr/lib/php/build/Makefile.global, should be -r--r--r-- , they are -r-xr-xr-x
Owner and group corrected on ./usr/lib/php/build/Makefile.global
Permissions corrected on ./usr/lib/php/build/Makefile.global
Permissions differ on ./usr/lib/php/build/acinclude.m4, should be -r--r--r-- , they are -r-xr-xr-x
Owner and group corrected on ./usr/lib/php/build/acinclude.m4
Permissions corrected on ./usr/lib/php/build/acinclude.m4
Permissions differ on ./usr/lib/php/build/mkdep.awk, should be -r--r--r-- , they are -r-xr-xr-x
Owner and group corrected on ./usr/lib/php/build/mkdep.awk
Permissions corrected on ./usr/lib/php/build/mkdep.awk
Permissions differ on ./usr/lib/php/build/phpize.m4, should be -r--r--r-- , they are -r-xr-xr-x
Owner and group corrected on ./usr/lib/php/build/phpize.m4
Permissions corrected on ./usr/lib/php/build/phpize.m4
Permissions differ on ./usr/lib/php/build/scan_makefile_in.awk, should be -r--r--r-- , they are -r-xr-xr-x
Owner and group corrected on ./usr/lib/php/build/scan_makefile_in.awk
Permissions corrected on ./usr/lib/php/build/scan_makefile_in.awk
Permissions differ on ./usr/lib/system/libmathCommon.A.dylib, should be -r-xr-xr-x , they are -rwxr-xr-x
Owner and group corrected on ./usr/lib/system/libmathCommon.A.dylib
Permissions corrected on ./usr/lib/system/libmathCommon.A.dylib
Permissions differ on ./usr/libexec/dumpemacs, should be -r-sr-xr-x , they are -r-xr-xr-x
Owner and group corrected on ./usr/libexec/dumpemacs
Permissions corrected on ./usr/libexec/dumpemacs
Permissions repair complete
The privileges have been verified or repaired on the selected volume
Then I sometimes get the brown screen that states,You must re-start your computer.
I have already zeroed out the hard drive and re-installed Panther and the upgrade Tiger disc.
I repair permissions using the Tiger disc upgrade.
Can anyone help me with this??

> I repair permissions using the Tiger disc upgrade.
One thing to note... When running Repair Disk Permissions, it is best to run it while started up normally, from your normal startup disk, not from a Mac OS X installation disc. The only time you should run it while started up from an installation disc is if some problem is preventing you from starting up normally. OTOH, Repair Disk can only be used when starting up from a different disk (such as an installation disc).
So, I would start up normally, run Disk Utility, and use Repair Disk Permissions on your normal startup disk.
NOTE: Repair Disk Permissions often gives alerts messages that can be ignored. They are more "informational," not serious errors.
http://support.apple.com/kb/TS1448
You should still run it periodically. When you run it, what needs to be repaired has been repaired; consider the rest of it an FYI. I've never experience a problem, where a Repair Disk Permissions message actually caused a problem. But, if you ever get an error while running Repair Disk (or Verify Disk), that is usually a serious problem.

Repairing disk permissions keeps giving same message

I routinely verify my HD and repair disk permissions. The latter often indicates repairs are needed, especially after installation of new software or updates (I repair before and after). But once repaired, if I verify the permissions they come out ok -- i.e., no repairs are needed. Until just recently. I am now getting the following message after repairing permissions:
Verify permissions for “Macintosh HD”
Determining correct file permissions.
Permissions differ on ./private/var/log/secure.log, should be -rw------- , they are -rw-r-----
Permissions verification complete
The privileges have been verified or repaired on the selected volume
If I verify permissions after repairing this, I get the same message again. So the repair is not holding. I am running OS X 10.4.11 and I recall that on earlier OS's there were sometimes innocuous repairs that kept being required, but that were not really a problem. But under 10.4.11 a repair has usually been good, and clears the deck. Until now. Any ideas?
Update: I am no longer having this problem. Possibly I was clicking on the verify permissions button instead of the repair button. I have used DU many times, so this would be a fairly boneheaded thing to do at this point. Maybe familiarity breeds carelessness? In any event, I often get the message above when I check disk permissions, and I would be curious to know why it is one of the more common repairs needed. So let's make that my question instead...
TIA
Message was edited by: Drake Bradley

Not to worry about it, that secure.log is a common one for that.
Repair Permissions checks Library>Receipts to find out the proper Permissions, that file's Permissions may exist in more than one and/or some OS component doesn't know the new/latest permissions when using it.

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

Repair disk permissions "greyed out"

Similar Messages

Maybe you are looking for