Which volume to repair permissions?

Perhaps this is a dumb question -- but there are none of those, right -- but which volume do I select when I repair permissions? There are two there. One says Macintosh HD (Mac OS Extended Journaled) the other says 37.3 GB Fujitsu MHT20. I usually do the process on both of them. Is this necessary?
Thanks in advance...

but which volume do I select when I repair permissions?
You can select either. Unless you've partitioned the drive, both of those items are treated the same for most tasks.
Is this necessary?
No.
(30895)

Similar Messages

Which Forum for "Repair Permissions" problems?

To which Forum do you submit "Repair Permissions" problems?

Thanks, Luke.
My permissions keep coming out as below. Doesn't seem right to me.
Steve
Repairing permissions for “Macintosh HD”
Reading permissions database.
Reading the permissions database can take several minutes.
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/DVD.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSettings.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSources.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Movies.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Music.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Photos.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Podcasts.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/TV.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/BackRow.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "Applications/iTunes.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "Applications/iTunes.app/Contents/Frameworks/InternetUtilities.bundle/Contents/ CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "Applications/iTunes.app/Contents/Resources/iTunesHelper.app/Contents/CodeResou rces", should be -rw-rw-r-- , they are lrw-rw-r-- .
Warning: SUID file "System/Library/Filesystems/AppleShare/afpLoad" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/Install.framework/Versions/A/Resources/runner " has been modified and will not be repaired.
Warning: SUID file "usr/bin/setregion" has been modified and will not be repaired.
Warning: SUID file "System/Library/Printers/IOMs/LPRIOM.plugin/Contents/MacOS/LPRIOMHelper" has been modified and will not be repaired.
Permissions differ on "System/Library/CoreServices/RawCamera.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iLifeMediaBrowser.framework/Versions/A/CodeRe sources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/CodeResourc es", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/BlackAndWhiteEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/CubeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/DissolveTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/DropletTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/FadeThroughBlackTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/FlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/MosaicFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/MosaicFlipTransitionSmall.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/PageFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/PushTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/RevealTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/SepiaEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/TwirlTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/WipeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Permissions repair complete

Verify/Repair permissions dimmed

Disk utility/verify/repair permissions are dimmed - maybe resulting from some new programmes downloaded recently. I have been able to verify/repair disk in installation option but this has not resolved the problem. All appears to work but obviously I would prefer to correct this little matter.I have some (but not a lot of) knowledge so hope the solution is going to be easy. I would prefer not to have to re-install OSX for obvious reasons.
Thanks in anticipation.
Den.

Hi Dennis,
first of all: WELCOME TO THE DISCUSSIONS!
Are you sure you mean "Repair permissions"? Mind that you have 2 options in disk utility:
1. Repair disk
2. Repair permissions
In order to repair the disk you have to boot from the install CD or another bootable volume.
Repair permissions should be done when booted from the hard disk.
In both cases make sure you select the disk in the left sidebar.

Repair Disk / Repair Permissions -- which first

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

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

Repair Permissions - Drive or Volume?

Promise not to laugh, OK?
When one occasionally performs Repair Permissions, should you perform it on the drive, or the volume?
Is anything possibly "missed" by performing it on the volume only? Or vice versa?

That's normal. The partition map takes up some of the space on the drive, so a single volume that fills the drive will never be as large as the drive itself. Similarly, a volume has all kinds of data structures for keeping track of files, so it will never have as much free space as the size of the volume's partition.
Note that repairing permissions only repairs the permissions of system files and applications with known permissions. All that extra stuff is completely irrelevant. If you need to repair the disk structures, you need to use Repair Disk instead of Repair Permissions.

Please Help, After Kernel panic restart failed- apple swirl(6 hrs), SafeMode-failed, SUMode-sucess. Could not unmount disk to erase. Repair permissions-multiple fail errors:unable to set permissions on... unable to set owner and group...

Please Help, I deleted an account that was the same name as the administrator but was not the administrator. Also a samsung galaxy s phone was charging through the usb port.
I closed out a program and got a message that the temp file could not be stored/saved.
Then a Kernel panic message occurred and restart was necessary.
The restart resulted in the screen with the apple logo and a continous swirl for 6+hrs,
Attempted Safe Mode start up, unsuccessful,
Single User Mode-sucess.
Ran $ fsck_hfs -rfd /dev/disk0s2 Ran several times repairs made with one which remained. something about a node.
No change in start up attempts
Started with install CD matching current OS 10.6
Ran Disk Utility Repair Permissions resulting in multiple errors:
One line/error
Warning: SUID file /////Ardagent has been modified and will not be repaired
144 lines/errors of this type of series of lines
Group permissions differ on...should be drwxr-xr-x, they are -rw-r--r-- .
permissions differ on...should be drwxr-xr-x, they are -rw-r--r-- .
unable to set owner and group...error 22: Invalid Argument
unable to set permissions on...error 22: Invalid Argument
Ran Repair Disk, result:
Error: Could not unmount disk (in red)
Ran Verify Disk, result:
The volume HD appears to be ok (in green)
Next I attempted to erase the dist to start from scratch since I have data backed up on time machine.
Error message box
Volume Erase failed
Volume Erase failed with error:
Could not unmount disk
I am looking to solve without buying DiskWarrior unless only resort.

So it looks like solved it for now I will update later. What I did was after starting from the install cd for the 10.6 system I ran from terminal ran:
diskutil disablejournaling /dev/disk0s2
diskutil disableownership /dev/disk0s2
diskutil repairPermissions /dev/disk0s2
then i closed terminal and then when to disk utility and chose to repair disk with results all was fine. Then ran repair permissions and got similar results from terminal function next I erased disk and then chose to restore from time machine and it is now restoring! yea!

Can you run Tiger and OS 8.6 on the same computer? RE: Repair Permissions

Hello,
I don't fully understand how "Repair Permissions" work and when it is needed and therefore I would like to post this question for some clarification. Using "Repair Permissions" for troubleshooting is a controversial issue. I read this interesting opinion about Repairing Permissions and now I am concerned that it may not be safe for me to install my old OS 8.6 on my OSX installed computer due to a "permission" conflict between OS 8 and OS X.
Could someone confirm this with me please? Could this cause some file permission problems?
I would use OS 8.6 to run my older Adobe Illustrator 8 application and photoshop 6. And then I will boot onto Tiger for everything else. I would switch a few times per day back and forth.
Basically, is it safe to run Tiger on the same computer that has OS 8.6 installed on it? (I am not concerned about making 8.6 run in the Classic environment because I know that doesn't work - I am refering to having separate bootable installs)
[1] http://www.unsanity.org/archives/000410.php
PS I am aware of how to change my startup OS on this particular computer (b&w G3). I would have to have the two OSs on the same volume and launch X by pressing x -key during startup due to the fact that OS 8.6 doesn't have the Startup Disk feature introduced in OS 9. That was an earlier separate discussion that has since been solved.
PS
I could choose to instead use my OS 9.2 but I have reserved that OS for another computer unfortunately. However depending on the outcome of this post, I might have to reconsider.

This is a really difficult issue to resolve! Apple doesn't have much documentation that covers running OS 8 & OS X on the same drive. There are, however, a few things that it might helpful to know:
1. Repairing permissions with Disk Utility in OS X won't touch user-created files. It only repairs things that have a receipt file, which are created by installers. The unsanity reference explains this; you might want to review that part of the article again.
2. Disk Utility has a separate repair OS 9 permissions function (accessed in the menus), but AFAIK, this only repairs permissions on the OS 9 system folder "blessed" by the Classic system pref as the one to use for Classic. I doubt this would be useful for the OS 8.6 system.
3. Of greater concern than mis-set permissions is file system damage. Under no circumstances should you use any disk repair utility on a Tiger drive except those that "know" about Tiger's file structure. This rules out using Disk First Aid from either OS 8 or OS 9, or any OS 8 or 9 third party utilities. (See this Apple document for the details.) I don't know if this also applies to OS 8's 'rebuild desktop' function, but I would avoid it to be on the safe side.
4. If you do decide to reformat or partition your drive for dual booting (as you mentioned in your other thread), do so only with Tiger's Disk Utility & remember to check the 'install OS 9 drivers' option or you won't be able to boot into OS 8 or 9, even if you have a viable system folder for either on the drive. See this Apple document for more info.
5. In light of the above, it is well worth getting OS 9 to use with Tiger on your B&W, as long as any older apps you need to run are compatible with it. (There should be no need to use OS 8/9 with text files anyway, since OS X can handle all the old text formats.) In fact, unless you need to use some peripheral that has no OS X driver, you probably will do just fine by using Classic with the old apps, eliminating the need to reboot completely.
6. If you need to buy OS 9, one inexpensive source is OWC's Mac OS 9.1 - OEM CD. At $35, it is a cheap way to avoid the headaches of OS 8 with Tiger! Note that you can upgrade from this 9.1 version to 9.2.2 for free with Apple's updates available from the Mac OS 9: Available Updates web page.
Message was edited by: R C-R

Should I repair permissions before or after updating to Mac OS X 10.7.2?

Hi,
Should I repair permissions before or after updating to Mac OS X 10.7.2? or should I fix permissions before and after the update?

This is not a routine maintenance. Upgrades can be screwed up if the system that is upgraded is screwed up. I believe in a "better safe than sorry" approach. If you repair permissions and the hard drive prior to an upgrade then if there be a problem perhaps that problem will not propagate to the new upgraded system. If there are no problems doing the repairs is harmless.
When it comes to the topic of permissions repairs there are many opinions but not much fact. In other words there doesn't appear to be a formal analysis of whether repairing permissions is only useful when a permissions problem arises. But there is a lot of anecdotal evidence suggesting that a repair both before and after a major system upgrade can reduce the risk of problems.
This is my opinion on the matter. I do not generally disagree with Niel or MacJack, but as I said I prefer to be safe rather than sorry.
Here's my general approach:
How to Install Lion Successfully - You must have Snow Leopard 10.6.7 or 10.6.8 Installed
A. 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. Then select Disk Utility from the Utilities. 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.3.) if DW cannot fix the drive, then you will need to reformat the drive and reinstall Snow Leopard.
B. Make a Bootable Backup Using Restore Option of Disk Utility:
Open Disk Utility from the Utilities folder.
Select the destination volume from the left side list.
Click on the Restore tab in the DU main window.
Check the box labeled Erase destination.
Select the destination volume from the left side list and drag it to the Destination entry field.
Select the source volume from the left side list and drag it to the Source entry field.
Double-check you got it right, then click on the Restore button.
Destination means the backup volume. Source means the internal startup volume.
C. Important: Please read before installing:
If you have a FireWire hard drive connected, disconnect it before installing the update unless you will boot from this drive and install the update on it. Reconnect it and turn it back on after installation is complete and you've restarted.
You may experience unexpected results if you have installed third-party system software modifications, or if you have modified the operating system through other means. (This does not apply to normal application software installation.)
The installation process should not be interrupted. If a power outage or other interruption occurs during installation, use the standalone installer (see below) from Apple Downloads to update. While the installation is in progress do not use the computer.
D. To upgrade to Lion:
Purchase the Lion Installer from the Mac App Store. The download will start quickly. Lion is nearly 4 GBs so a fast internet connection is essential. Download time could run upwards of 4 hours depending upon network conditions and server demands at the time.
Boot From The Lion Installer which is located in your Applications folder.
Follow instructions for installation.

Repair Permissions in Single User Mode

So, I have searched various posts and have yet to find anything that has worked so far. Hopefully, someone can still help. I recently made the mistake of changing my permissions on my hard drive. I clicked "Get Info" for the Boot volume and changed the permissions for "Everyone." I thought I had corrected it, but now when I try to boot, it just sits at the apple grey screen with the spinner and never loads the OS. Judging from other comments, this appears to be a permissions issue and all I need to do is repair the permissions which is why I ran through these commands in Single User mode:
/sbin/fsck -fy<return> --I did this twice to fix the drive
/sbin/fsck -fy<return>
/sbin/mount -uw<return>
/sbin/autodiskmount -va <return>
/usr/sbin/diskutil repairPermissions /<return>
sudo diskutil repairPermissions /
I am having to run through the Single User mode because I do not have the SL install disk. However, I have Windows installed on a Boot Camp partition and I can access files on the mac side but everything is read only.
I am a novice at the command line so any guidance on what commands might help to repair permissions would be great.

Found this for Leopard. Will probably work in 10.6
Run these commands and hit enter after each. Be careful with the spaces; keep exactly as written. There are various suggestions in this thread, which you might first want to check out, but this seems to be the most promising.
http://forums.macnn.com/90/mac-os-x/370223/changed-hd-permissions-mac-wont-get/
mount -uw /
chmod 775 /
chmod 1775 /
Then restart
BTW, not recommended to repair Permissions from the install disk, since if you've updated since installing, those will be out of date and incorrect. Permissions Repair should be done from the normal boot volume.
Message was edited by: WZZZ

Repairing permissions failure

My system crashed this week. I lost all the apps. The whole thing was backed up via Time machine
To get it back into the proper order, I first installed the original OS which was 10.3 The I ran Mac hardware Test, which told me i had 2 bad memory modulesw. I pulled them out, and MHT then told me memory was OK.
Then i ran Disk Warrior from disk. This fixed a very screwed up directory.
Once that was fixed, i installed 10.5.6. After that, my G5 booted up OK, but I had none of my applications nor their library support files. So i did a file-by-file Time Machine recovery, mostly for various application support files plus the apps themselves. Meanwhile, Software Update was telling me to download 10.8. It was a good idea, since i need 10.8 to run Protools. After 2 hours, the 700+ gb file got onto my desktop, but it wouldn't load, citing an install error. I suspected that permissions might be some part of the problem.
I have just run verify permissions and repair permissions. Neither will do their job. Both gave me the message: "The underlying task reported failure on exit."
One thought i have is, because of all this uploading installing, perhaps i am not using the correct version of DU for OS 10.5.6. What i have is 11.1 is that right?
Any advise about how to get disk utility back on track is much appreciated. Is there a good 3rd party permission repair utility that will tell me where the file structure is remiss? At this point, after 3 days of trying to recover from a system wide crash caused by failed memory and trashed directories I am feeling very burned out. My next option is too reinstall by wiping the drive clean. Obviously, I'd prefer not to do that, since ZI feel i am so close to being back in the saddle. Any help is much appreciated.

Try 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, Leopard or Snow 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 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.

Repairing permissions frequently - daily

Can anyone shed light on this puzzle?: I have to repair permissions at least 2 or 3 times every day. I generally run only Mail 2.1.3, Safari 3.1.2, Filemaker Pro 5.5v2, Quickeys 3.2.3, and a small number of always-on gadgets (Sidenote, TypeIt4Me, Alarm Clock 2, NetBarrier - all current versions). I'm almost always running Safari and I do go through lots of tabs in a session (a minimum of about 500 each day), but I close excess tabs regularly (wish Safari would do that automatically!), and I relaunch Safari several times each day.
At least 2 or 3 times every day, Safari slows to a crawl and I use Oasis to repair permissions. It's almost always the same group of permissions that need repair. Here they are:
Started verify/repair permissions on disk disk0s3 Macintosh HD
Determining correct file permissions.
Group differs on ./Applications/Utilities/Activity Monitor.app/Contents/Resources/pmTool, should be 80, group is 0
Owner and group corrected on ./Applications/Utilities/Activity Monitor.app/Contents/Resources/pmTool
Permissions corrected on ./Applications/Utilities/Activity Monitor.app/Contents/Resources/pmTool
Group differs on ./Applications/Utilities/Keychain Access.app/Contents/Resources/kcproxy, should be 80, group is 0
Owner and group corrected on ./Applications/Utilities/Keychain Access.app/Contents/Resources/kcproxy
Permissions corrected on ./Applications/Utilities/Keychain Access.app/Contents/Resources/kcproxy
Group differs on ./Applications/Utilities/ODBC Administrator.app/Contents/Resources/iodbcadmintool, should be 80, group is 0
Owner and group corrected on ./Applications/Utilities/ODBC Administrator.app/Contents/Resources/iodbcadmintool
Permissions corrected on ./Applications/Utilities/ODBC Administrator.app/Contents/Resources/iodbcadmintool
The privileges have been verified or repaired on the selected volume
Verify/repair finished permissions on disk disk0s3 Macintosh HD
Can anyone shed some light on why this happens so frequently, and what I might do about it? I've tried running Activity Monitor to see if that would tell me anything, but either it doesn't or I don't know what to look for.

If you were having any serious problems with your Mac you might as well complete the exercise by repairing your hard disk as well. You cannot do this from the same start-up disk. Reboot from your install disk (holding down the C key). Once it opens, select your language, and then go to Disk Utility from the Utilities menu. Select your hard disk as before and click Repair.
Once that is complete reboot again from your usual start-up disk.
More useful reading here:
Resolve startup issues and perform disk maintenance with Disk Utility and fsck
http://support.apple.com/kb/TS1417
Then try this:
(First, if yours is an Intel Mac, check that Safari is not running in Rosetta, which is enough to slow it to a crawl.)
Many, including me, have had success with adding DNS codes to their Network Settings, with good results in terms of speed-up:
Open System Preferences/Network. Double click on your connection type, or select it in the drop-down menu. Click on TCP/IP and in the box marked 'DNS Servers' enter the following two numbers:
208.67.222.222
208.67.220.220
Click on Apply Now and close the window.
Restart Safari, and repair permissions.
If that didn't do it, then try this as well:
Empty Safari's cache (from the Safari menu), then close Safari.
Go to Home/Library/Safari and delete the following files:
form values
download.plist
Then go to Home/Library/Preferences and delete
com.apple.Safari.plist
Repair permissions (in Disk Utility).
Start up Safari again, and things should have improved.

Volume needs repair AND hard drive problem...

OK so I have an Intel Based iMac and its about 1 year old. Randomly I got a message saying that the hard drive disc space is almost full, which makes NO sense. I have a 250 hard drive and I use it mainly for video editing. Before I got this message, I had about 100 GB left on my hard drive. I have NO CLUE where 100 GB went to, and i know it was not from video. Also I went to the disk utility and it said "Volume needs repair" and it gave me an "The underlying task reported failure,". Im not sure what to do and I'm hoping you guys will.....if this has been asked before, I apologize.

Yes, you can delete it, but it indicates a bigger concern namely your maintenance scripts aren't running regularly to clean up the logs or you have a problem in the system or an application that is writing huge amounts of information constantly into the log file. You should check the log using the Console application (Utilities folder) and examine its content to see if this is the case.
You should also read the following for information on installing utilities that can assure the maintenance scripts are run as well as other information on system maintenance that can help keep your computer running better.
Kappy's Personal Suggestions for OS X Maintenance
For disk repairs use Disk Utility. For situations DU cannot handle the best third-party utilities are: Disk Warrior; DW only fixes problems with the disk directory, but most disk problems are caused by directory corruption; Disk Warrior 4.0 is now Intel Mac compatible. TechTool Pro provides additional repair options including file repair and recovery, system diagnostics, and disk defragmentation. TechTool Pro 4.6.1 is Leopard compatible; Drive Genius is similar to TechTool Pro in terms of the various repair services provided. The current version, 1.5.1, is Intel Mac compatible.
OS X performs certain maintenance functions that are scheduled to occur on a daily, weekly, or monthly period. The maintenance scripts run in the early AM only if the computer is turned on 24/7 (no sleep.) If this isn't the case, then an excellent solution is to download and install a shareware utility such as Macaroni, JAW PseudoAnacron, or Anacron that will automate the maintenance activity regardless of whether the computer is turned off or asleep.
OS X automatically defrags files less than 20 MBs in size, so unless you have a disk full of very large files there's little need for defragmenting the hard drive. As for virus protection there are few if any such animals affecting OS X. You can protect the computer easily using the freeware Open Source virus protection software ClamXAV. Personally I would avoid most commercial anti-virus software because of their potential for causing problems.
I would also recommend downloading the shareware utility TinkerTool System that you can use for periodic maintenance such as removing old logfiles and archives, clearing caches, etc.
For emergency repairs install the freeware utility Applejack. If you cannot start up in OS X, you may be able to start in single-user mode from which you can run Applejack to do a whole set of repair and maintenance routines from the commandline. Note that presently AppleJack is not compatible with Leopard.
When you install any new system software or updates be sure to repair the hard drive and permissions beforehand. I also recommend booting into safe mode before doing system software updates.
Get an external Firewire drive at least equal in size to the internal hard drive and make (and maintain) a bootable clone/backup. You can make a bootable clone using the Restore option of Disk Utility. You can also make and maintain clones with good backup software. My personal recommendations are (order is not significant):
1. Retrospect Desktop (Commercial - not yet universal binary)
2. Synchronize! Pro X (Commercial)
3. Synk (Backup, Standard, or Pro)
4. Deja Vu (Shareware)
5. PsynchX 2.1.1 and RsyncX 2.1 (Freeware)
6. Carbon Copy Cloner (Freeware - 3.0 is a Universal Binary)
7. SuperDuper! (Commercial)
8. Data Backup (Commercial)
The following utilities can also be used for backup, but cannot create bootable clones:
1. Backup (requires a .Mac account with Apple both to get the software and to use it.)
2. Toast
3. Impression
4. arRSync
Apple's Backup is a full backup tool capable of also backing up across multiple media such as CD/DVD. However, it cannot create bootable backups. It is primarily an "archiving" utility as are the other two.
Impression and Toast are disk image based backups, only. Particularly useful if you need to backup to CD/DVD across multiple media.
Visit The XLab FAQs and read the FAQs on maintenance, optimization, virus protection, and backup and restore.
Additional suggestions will be found in Mac Maintenance Quick Assist.
Referenced software can be found at www.versiontracker.com and www.macupdate.com.

10.5.4 upgrade failure - can't repair permissions: "no valid packages"

I just ran the 10.5.4 combo updater to upgrade from 10.5.3 but now I can't boot into the main boot drive (get the circle with line through it instead of login screen). Fortunately I have Panther on another drive and was able to boot into it via the Leopard install disk Startup Drive utility. From there I've run Disk Utility and Techtool Deluxe which reports the Leopard drive is okay, but when I run Repair Permissions on that drive I get the following error:
Repairing permissions for “HD One”
Error: No valid packages (-9997)
Permissions repair complete
From the other posts about problems with 10.5.4 upgrade it looks like I have to run an Archive and Install of 10.5.0 again and then upgrade from there, but is there a problem with the drive that I need to attend to first?
Further complicating things is that the Leopard boot drive is a 320gb drive that was partitioned to a 120gb main drive + second using Speedtools ATA Cap drive utility because this G4PM can't recognize larger size drives. So I'm reluctant to do an erase of the main drive and then reinstall of Leopard.
Any suggestions?

I have Panther on another drive and was able to boot into it via the Leopard install disk Startup Drive utility. From there I've run Disk Utility and Techtool Deluxe which reports the Leopard drive is okay, but when I run Repair Permissions on that drive I get the following error:
Repairing permissions for “HD One”
Error: No valid packages (-9997)
Bad move trying to repair a Leopard disk with something from Panther or Tiger. They're not compatible. As for the permissions, the receipts structure is totally different that's why it can't do the job.
As for using the SpeedTools thing, I have no idea. Your best bet is to get another ext FWHD and install Leopard onto to it, use the Migration Assistant to transfer your stuff from the hosed volume, and see if that works. If so, then use Carbon Copy Cloner or SuperDuper! to clone the FWHD installation to the hosed volume.

Repair Permissions with/without Tiger disk?

I was wondering what the best way is to repair permissions. Should one repair them booting off the Tiger disk or can one just open disk utility and repair the permissions while running on their hard drive?
Also, my new iMac came with two disks. I also have a Tiger disk from when I purchased Tiger for my PowerBook. If it is necessary to repair permissions from the disk, which disk should I use? Can I use the Tiger disk or should I use one of the disks that came with my iMac?
Thanks!

Regarding your first question, it makes no difference so there isn't any need to boot from the install disc to repair disk permissions.
Regarding your second question, the same applies but you should use the Tiger install package that shipped with your new iMac to run repair disk via Disk First Aid when booted from the iMac's install disc on your iMac's boot volume which is much more important than repairing disk permissions.
The Tiger retail install package is not Universal - it is for a Mac with a PPC processor only and your new iMac has an Intel processor.
Check this link for system troubleshooting procedures which includes running repair disk, repairing disk permissions and system and user cache cleaning.
http://www.thexlab.com/faqs/repairprocess.html
And this link for recommended maintenance for OS X which isn't much focusing on the Maintenance Myths section.
http://www.thexlab.com/faqs/maintainingmacosx.html
And this link about running repair disk via Disk First Aid.
http://www.thexlab.com/faqs/durepairfns.html

Repair Permissions Feedback ?

I usually repair permissions about once a week or so and find that it repairs the same thing almost every time? I am just wondering what exactly it is and why it keeps having to be repaired? Any help would be appreciated.
Repairing permissions for “Macintosh HD”
Determining correct file permissions.
Permissions differ on ./private/var/log/secure.log, should be -rw------- , they are -rw-r-----
Owner and group corrected on ./private/var/log/secure.log
Permissions corrected on ./private/var/log/secure.log
Permissions repair complete
The privileges have been verified or repaired on the selected volume
Thanks
MBP Mac OS X (10.4.8) 1.83GHz 15.4" 2GB

That message means that the weekly cron task has been run since you last used the repair permissions command; this task sets the permissions on the secure.log file as well as several others to -rw-r----- after rotating the logs, which allows all admin users to read the log. The repair permissions command changes them to -rw------- to keep the secure.log file secure, with only root able to read or change the log's contents.
(20103)

Which volume to repair permissions?

Similar Messages

Maybe you are looking for