Verify Permissions in Disc Util.

Verifying permissions on HD after a start-up. After 6 min.of barber pole, verify estimated time is 6 hrs. 5 more min, jumps to 3 hrs, slowly works down to finish at the 18 min. mark per Log.
My 500 GB HD only has 62.6 GB usage, OSX Extended (journaled), 459000 files
Time Machine is activated but not backing-up
There are 2 users
My new stuff post MBP Lion
Old stuff from 9 yr old G3
Is this amount of time normal under these conditions?

I wouldn't worry about it if everything is running normally. I wouldn't even worry about repairing permissions unless you encounter problems.
Wait to see if others with a MBP post their times.

Similar Messages

Running "verify permissions" in Disk Utility freezes the Macbook

Ever since I received my new Macbook, whenever I try to run the Disk Utility's "verify permissions", the system freezes up. Disk Utility seems to freeze, and I cannot interact with anything on the computer anymore. The mouse remains functional, but I cannot click on any other applications, change focus or even force quit.
Any ideas? Thanks in advance!

I always thought it was a bad idea to repair permissions from a disk other than the startup disk if you had updated the OS from what is on the install DVDs.
Don't bother with verifying permissions as it takes as long as repairing them. Have you tried a straight repair of them instead? How about running that from a program like Cocktail?

Cannot verify permissions from Disk Utility

I'm a new Mac user, and I've undoubtedly deleted or moved files to incorrect places.
I can run DU and verify my disk, which appears to be okay, but when I choose the Verify Permissions tab, I get the message that permissions validation failed because "there are "no valid packages." After 23 years of PC use, I can't fathom this arcane message.
Can anyone help?
Thanx, Linnie
2 GB RAM
160 GB internal SATA
500 GB G-Tech Mini external SAT

Rajesh Sharma wrote:
I'm a new Mac user, and I've undoubtedly deleted or moved files to incorrect places.
You probably haven't, unless you've been in the system files on the hard drive.
Are you trying to repair permissions because something is wrong? or just as regular maintenance?
If you've selected the Hard Drive from the panel on the left - and it's the correct Hard Drive rather than a partition it should repair.
You could try starting up from your install DVD1. As soon as you get to a menu at the top - go to utilities and run Disk Utility from there and see if you can repair.
No valid packages would indicate no OSX on the drive.
Hope that helps. Get back and we'll work it out.
Best of luck.
Rajesh Sharma wrote:
Hi,
Just regular maintenance.
If "no valid packages would indicate no OSX on the drive," how would my system be running without an OS. I realize this sounds like "duh," but I'm serious. I will try booting from DVD1 tomorrow and see what happens
Thanx,
Linnie.

Every time I use Repair Disc Permissions under Disc Utility, I get the following message: Permissions differ on "System/Library/MonitorPanels/Profile.monitorPanel"; should be drwxr-xr-x ; they are lrwxr-xr-x .

Can anyone explain this? Every single time I use Disk Utility to repair disk permissions, I get the same messages, not just for Monitor Panels, but for every single item in the Library!!!, and this wastes a lot of time because once the permissions have been repaired, I find that the messages come up again immediately, suggesting that the repairs were not made!! The messages always read as follows: should be drwxr-xr-x ; they are lrwxr-xr-x .
What is going on here, and how can I fix it permanently?

The structure of those packages changed in an update. There's nothing to fix.
The repair permissions function should only be used when troubleshooting an issue, and then only once per incident. Running it repeatedly won't fix anything.
(93748)

Disc Utility always set wrong permissions of the startup disc

The permissions of the startup disc should be "drwxrwxr-t 39 root admin", right?
But everytime I repair my permissions with disc utility I get the (german) message:
Benutzer unterscheidet sich für ., Soll-Wert: 501, Ist-Wert: 0
Die Gruppe unterscheidet sich für ., Soll-Wert: 501, Ist-Wert: 80.
Die Zugriffsrechte unterscheiden sich für ., Soll-Wert: drwxr-xr-x , Ist-Wert: drwxrwxr-t .
And the permissions of the startup disc are set to:
drwxr-xr-x 39 Nomis101 Nomis101
(I've read that out with "$ ls -ld /")
Than I "repair" the permissions with "$ chmod 1775 /". And next time I use disc utility I have the same again.
I've repaired the permissions in single user mode, I've booted from the install DVD and reseted my ACLs, I've removed my ACLs. But nothing seems to help.
Sometimes I also have the issue that I cannot move any file on my desktop anymore or that I have suddenly no write permissions in the folder /Volumes/Macintosh HD
I suspect MacPorts 1.7 or Mercurial as the malefactor, because the issues accumulate after I've done something with MacPorts (or Mercurial). But I'am not sure with that.

{quote:title=V.K. wrote in another thread...:}If I'm not mistaken you told me once a while ago how to modify permissions database which seems to be required there.{quote}
Hmm, that's actually a bit of a tough one - Sorry, but I think it's beyond me.
My understanding of the permissions database consists of only what I have been able to piece together from tinkering, and while I have been able to edit individual entries and have "repair permissions" behave as expected with the edits, "/" is a bit different.
Basically, every time something is installed that results in an update to the permissions database, entries are added, i.e. the entry for a file isn't edited but rather a whole new entry is added. That applies to a given file in the update, as well as every folder on the path to that file. Since installations are pretty much all rooted in "/", that means a new entry for "/" is created every time any installer updates the receipt database, and other things may add entries as well -- I have 88 entries for "/" in there on my system. This does't display all of the entries, but a slightly more user-friendly way is to view most of them is to use:<pre>
pkgutil --file-info /</pre>
I haven't dug that deeply, but I don't know what determines which entry will be used during the actual permissions verification / repair operation (it's been a while but I seem to recall that it wasn't as simple a matter as "most recent", for example), so figuring out which one to edit might be a challenge.
And there are cases like "/" where there are entries in the database, but as you pointed out, that seem to be ignored when repairing of verifying permissions, and I have no idea what flags the system to ignore those.
Interestingly, of the 88 entries on my system, 83 call for "1775" permissions, but 5 of them (mostly "Safari" updates but also the "BaseSystem" package) actually say the permissions should be "1755"...
I think for the OP, the bigger issue is trying to figure out (and stopping) whatever it is that keeps wrecking security by changing the ownership to the user...

Repair/Verify Permissions hanging...

hi!
this is my first post on here and i'm hoping someone can help me. i have osx 10.5.2 installed on 2 separate hard drives and on both of those, when trying to run the repair or verify permissions in disk utility, it hangs with the progress bar about 1/4 way done. does anyone know why this is, and how do i fix/get around this problem? thanks in advance for any help.

How long did you wait? The Repair Permissions with Leopard takes much longer than it did in Tiger.
Times reported in this forum have been reported as long as 4 to 40 minutes.
It goes about a forth of the way and says 1 Minute remaining and stays there for a while (last time I did it, I timed it as about 5 minutes), and then it reports another time, which is also usually inaccurate and much longer than it actually takes.
Be patient and let it run. Get some coffee or go for a walk.

During a routine verify permissions using my disc utility, I'm getting a WARNING: SUID file "Systems/Library/CoreService-.ent" has been modified and will not be repaired.

During a routine verify permissions using my disc utility, I'm getting a WARNING: SUID file "Systems/Library/CoreService….ent" has been modified and will not be repaired. What does this mean?? I'm not awawre that I did anything to cause this and is it somethingI should try to fix?

1. It means that the current software is installed.
2. It's not something you should try to fix.
3. Verifying and repairing permissions shouldn't be done as routine tasks.
(94115)

Lion Disc Utility won't repair permissions

I purchased a MacBook Pro that came with Snow Leopard loaded. I was given a free Lion upgrade, which I downloaded. When I ran Disc Utility to repair Permissions I get a long list of "library" errors that are supposedly repaired. However, when I ran it again to verify the repair, all of the errors were back. I did this 4 times, restarting twice, then called Apple who walked me through the repair and it still didn't work.
I surmise the errors are the result of loading Lion over Snow Leopard since my Mac Mini that came with Lion doesn't have the problem. Are these library errors anything to worry about? Anyone know if Apple's working on the problem?
Thanks,
Linda

here you go .... This makes the 7th time I've "repaired permissions" and I get the same list each time.
Repairing permissions for “Hard Drive”
Permissions differ on “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Rem ote Desktop Message.app/Contents/Resources/pl.lproj/UIAgent.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Rem ote Desktop Message.app/Contents/Resources/pl.lproj/UIAgent.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreen.app/Contents/Resources/pl.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreen.app/Contents/Resources/pl.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pl.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pl.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Rem ote Desktop Message.app/Contents/Resources/pt_PT.lproj/UIAgent.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Rem ote Desktop Message.app/Contents/Resources/pt_PT.lproj/UIAgent.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreen.app/Contents/Resources/pt_PT.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreen.app/Contents/Resources/pt_PT.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pt_PT.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pt_PT.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Rem ote Desktop Message.app/Contents/Resources/pt.lproj/UIAgent.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Rem ote Desktop Message.app/Contents/Resources/pt.lproj/UIAgent.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreen.app/Contents/Resources/pt.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreen.app/Contents/Resources/pt.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pt.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/pt.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Rem ote Desktop Message.app/Contents/Resources/sv.lproj/UIAgent.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Rem ote Desktop Message.app/Contents/Resources/sv.lproj/UIAgent.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreen.app/Contents/Resources/sv.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreen.app/Contents/Resources/sv.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/sv.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/sv.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Rem ote Desktop Message.app/Contents/Resources/ru.lproj/UIAgent.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Rem ote Desktop Message.app/Contents/Resources/ru.lproj/UIAgent.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreen.app/Contents/Resources/ru.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreen.app/Contents/Resources/ru.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/ru.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/ru.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Rem ote Desktop Message.app/Contents/Resources/no.lproj/UIAgent.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Rem ote Desktop Message.app/Contents/Resources/no.lproj/UIAgent.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreen.app/Contents/Resources/no.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreen.app/Contents/Resources/no.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/no.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/no.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Rem ote Desktop Message.app/Contents/Resources/fi.lproj/UIAgent.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Rem ote Desktop Message.app/Contents/Resources/fi.lproj/UIAgent.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreen.app/Contents/Resources/fi.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreen.app/Contents/Resources/fi.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/fi.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/fi.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Rem ote Desktop Message.app/Contents/Resources/da.lproj/UIAgent.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Rem ote Desktop Message.app/Contents/Resources/da.lproj/UIAgent.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreen.app/Contents/Resources/da.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreen.app/Contents/Resources/da.lproj/MainMenu.nib”
Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/da.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/da.lproj/MainMenu.nib”
Permissions repair complete

Disc Utility can't verify the HD

Today i had a problem with an application hangging everytime i tried to load it. So i went to Disk Utility to verify permissions, but first I decided to do a verification to the disc.
After 5 or 10 seconds i get an error saying (in spanish, so i will translate it) *Node structure no valid*.
Does anybody knows what this means and how to fix or repair this?
Thanks

Yes, it means you hard drive directory is damaged and needs repair. See:
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.
In the event you may need to reformat the drive, I suggest backing up your files ASAP.

Disc utility can not verify my internal harddrive

My disc utility cannot verify the internal harddrive and says that it needs to be repaired, however the repair button is greyed out. I have been told that I need the install a disc to repair the harddrive, my computer is running 10.4 Tiger, can I buy a 10.5 Leopard disc to install and repair the harddrive? or does it have to be the original 10.4 disc which unfortunately I no longer have? if so do you know where I can buy a 10.4 disc?
Thanks

Hi Rainbow King, and a warm welcome to the forums!
It's supposed to be OK to use a Leopard Install Disk to Repair Tiger HDDs, (though not Repair Permissions with it), but I've had real problems when I did.
Other options are...
A. Unfortunately, Disk Utility can't fix all that much, your best bet is DiskWarrior from Alsoft, you'll need the CD to boot from if you don't have another boot drive...
http://www.alsoft.com/DiskWarrior/
B. Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot.
PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.
C. Tough without the Tiger Disk problems, but try fsck...
To use fsck, you must run it from the command line. Unlike using your mouse to open an application to do something, you'll need to type a text command at the prompt (#) to tell fsck what to do. The Terminal application (/Applications/Utilities) and single-user mode are two examples of command-line interfaces in which you can type such commands. To use fsck:
1. Start up your computer in single-user mode to reach the command line. Hold CMD+s keys down at bootup. Note: If necessary, perform a forced restart as described in the Emergency Troubleshooting Handbook that came with your computer. On desktop computers, you can do this by pressing the reset/interrupt button (if there is one) or holding down the power button for several seconds. On portable computers, simultaneously press the Command-Control-power keys. If your portable computer doesn't restart with this method, you may need to reset the Power Manager.
2. At the command-line prompt, type /sbin/fsck -fy
(SPACE between fsck AND -fy important)
3. Press Return. fsck will go through five "phases" and then return information about your disk's use and fragmentation. Once it finishes, it'll display this message if no issue is found: 
The volume (nameofvolume) appears to be OK  If fsck found issues and has altered, repaired, or fixed anything, it will display this message: *** FILE SYSTEM WAS MODIFIED ***   Important: If this message appears, repeat the fsck command you typed in step 2 until fsck tells you that your volume appears to be OK (first-pass repairs may uncover additional issues, so this is a normal thing to do).
4. When fsck reports that your volume is OK, type reboot at the prompt and then press Return.
http://docs.info.apple.com/article.html?artnum=106214
Then Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.

Screen saver does not turn on. Have run the disc utility to repair disc permissions. Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.

screen saver does not turn on. Have run the disc utility to repair disc permissions. Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent” has been modified and will not be repaired.
I am running 10.9.1 software
Help Diggs1936

I would try reinstalling.
Reinstall Lion, Mountain Lion, or Mavericks without erasing drive
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair
When the recovery menu appears select Disk Utility. 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 then click on the Repair Permissions button. When the process is completed, then quit DU and return to the main menu. Select Restart from the Apple menu.
Reinstall Mountain Lion or Mavericks
OS X Mavericks- Reinstall OS X
OS X Mountain Lion- Reinstall OS X
OS X Lion- Reinstall Mac OS X
Note: You will need an active Internet connection. I suggest using Ethernet
if possible because it is three times faster than wireless.

I have an alert message in disc utility. Error: storage system verify or repair failed. Problems were found with the partitian map which might prevent booting.

While running verify disc in disc utility on 251 GB SSD SM256c Media I came up with this message: Alert system verify or repair failed. In the descriptions box of history it said, problems were found with the partitions map which might prevent booting. This is followed by a message in red reading, Error: Storage system verify or repair failed. At the time I was down loading raw pictures off my camera through a card reader across my computer to a relatively new 2TB Western Digital portable hard drive. after about 13 to 15 pictures downloaded that drive faileded. My Mac Book Air works fine, but i get this message now everytime I run disc verify on this disc. The Macintosh HD checks out fine.

While running verify disc in disc utility on 251 GB SSD SM256c Media I came up with this message: Alert system verify or repair failed. In the descriptions box of history it said, problems were found with the partitions map which might prevent booting. This is followed by a message in red reading, Error: Storage system verify or repair failed. At the time I was down loading raw pictures off my camera through a card reader across my computer to a relatively new 2TB Western Digital portable hard drive. after about 13 to 15 pictures downloaded that drive faileded. My Mac Book Air works fine, but i get this message now everytime I run disc verify on this disc. The Macintosh HD checks out fine.

I have downloaded Mountain Lion and Time Machine says that my Free Agent Goflex (Seagate) external 2gb drive cannot be used as it is read only. I tried disc utility to repair permissions but that block is greyed out. The disc verifies as being OKI

Since installing Mountain Lion, Time Machine says says that my Free Agent Goflex (Seagate) external 2gb drive cannot be used as it is read only. I tried disc utility to repair permissions but that block is greyed out. The disc verifies as being OKI What next?

Ok, I solved this problem! I ejected the drive and then disconnected it both from the power supply and the USB connector. I then reconnected everything and powered it up again and Then went into TM preferences and chose the drive as the backup. TM did a new backup (well over an hour) and now works as advertised.

When I run disk utility, verify permissions I get "WARNING SUID file system/Library/Coreservices/Remotemanagement/ARDAgent.app/Contents/MacOS/ARDAge nt has been modified

When I run disk utility, verify permissions I get "WARNING SUID file system/Library/Coreservices/Remotemanagement/ARDAgent.app/Contents/MacOS/ARDAge nt has been modified

Please read Disk Utility's Repair Disk Permissions messages that you can safely ignore.
Roger

Disk Utility Verify permissions question

I have always done, since 10.x, repair permissions via disk utility by opening disk utility app, selecting the top most icon:
"drive manufacturer and size" name
and then underneath: "Macintosh HD"
and then under that "my disc drive" name
I have always just selected the top most and hit repair.
Should I have been actually selecting "Macintosh HD" instead of the top one?

Should I have been actually selecting "Macintosh HD" instead of the top one?
In your case, it doesn't matter. The distinction is only relevant for drives which have two or more partitions.
(57605)

Verify Permissions in Disc Util.

Similar Messages

Maybe you are looking for