Verify/Repair Disk "in a loop"

Hi
I did notice high CPU usage which I narrowed down to a process mtmfs. I looked at https://discussions.apple.com/thread/3201661 and followed the steps to verify my disk. It resulted in telling me that my disk needs to be repaired. Please see inserted screen shot.
However when I follow the steps to repair the disk (CMD+R during startup, Disk Utility and Repair Disk) it tells me the the disk is ok, and therefore nothing is repaired.
If I do a verify disk after the "Repair" again, it shows the same message as shown at screen shoot.
Any idea how to get the problem resolved?
Thanks
Heiko

Live verification of the startup volume isn't reliable. You do not need Disk Warrior. Nobody who has backups needs it.
Delete the corrupt local snapshot database by turning Time Machine OFF and then back ON in its preference pane.

Similar Messages

  • Verify & Repair Disk Permissions VS. Verify and Repair Disk

    Is there a document that explains the differences in these two actions?
    Thanks.

    Hi Trevor,
    Repair Permissions and Verify or Repair disk are two separate processes.
    Repair Permissions is explained here.
    Verify/Repair Disk is explained here.
    -mj
    [email protected]

  • Verify/Repair disk permissions

    I heard that it's a good idea to verify and repair disk permissions. What does that do? And, when should I do it?
    -Eric

    Hi, again, Eric.
    My, we're curious today, aren't we?
    See:
    • My "The Repair functions in Disk Utility: what's it all about?" FAQ.
    • My "Maintaining Mac OS X" FAQ. It covers my advice on "regular maintenance" and dispels some common "maintenance myths."
    Good luck!
    Dr. Smoke
    Author: Troubleshooting Mac® OS X
    Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
    I may receive some form of compensation, financial or otherwise, from my recommendation or link.

  • Verifying/Repairing Disk Permissions

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

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

  • Verify/Repair disk permissions hangs

    Hello,
    Since yesterday my SL became kind of unstable and I have to reboot it because of a hang with a spinning wheel quite often.
    I want to verify/repair the disk permissions but the tasks never completes. When I run it via the GUI in the Disk Utility, it goes to around 5% then nothing happens even if I wait several hours. I can cancel the repair.
    I also tried to run it via the command line but the progress stays at 0% :
    ~ $ sudo diskutil verifyPermissions /
    Started verify/repair permissions on disk0s2 Macintosh HD
    0% ...............................................
    ~ $ sudo diskutil repairPermissions /
    Started verify/repair permissions on disk0s2 Macintosh HD
    0% ...............................................
    Any ideas ?
    Thanks,
    Tex

    From your description it sounds like the internal HD is failing. It should be under 1 year old so you are covered by the warranty, make an appointment ASAP with your local Apple Store or AASP to bring it in. In addition if you have not purchased AppleCare now is the time to get it, AppleCare will extend your warranty to 3 years. However you must buy it buy it within the first year of ownership!
    Here is a link you can use to make an appointment.
    Regards,
    Roger

  • Verify & Repair Disk Permissions never get completed

    I tried so many times on Verify Disk Permission, and Repair as well, however, both never get to complete the whole scanning process. I don't know what to do with it... Please help!!!
    G4   Mac OS X (10.2.x)  

    Hi KM, et al,
       I have a silly suggestion. Maybe if you corrected permissions by hand, it would fix the problem. Try the following commands:
    sudo chmod 644 /usr/share/man/man1/more.1
    sudo chown root:wheel /usr/share/man/man1/more.1
    You must execute the command as a system administrator and when prompted for a password, give the admin's password. I'm not sure what effect that will have though. /usr/share/man/man1/more.1 and /usr/share/man/man1/less.1 are actually hard links to the same file. On my system, changing one changes the other, which I don't believe is POSIX compliant. (but I haven't looked that up) Maybe that's one of the anomalies of linked files on HFS+ filesystems. However, I'm able to make the change on my system so it's certainly worth trying.
       I don't really know what's happened to your systems but it's certainly not something that should cause you to reinstall. At the very worst, you should be able to get a single copy of the file and recreate the links. The first step is to figure out what state your systems are in. What do you get when you execute the following command:
    ls -l /usr/share/man/man1/more.1 /usr/share/man/man1/less.1
    It would be most useful if you post the output you get before you try the fix in my previous paragraph.
    Gary
    ~~~~
       We cannot do everything at once, but we can do something
       at once.
             -- Calvin Coolidge

  • Verify/Repair disk corruption- disk utility on OS X CD not working...

    Hi Everyone....
    I have an Intel-based iMac that was running on Leopard until a few days ago. My sister-in-law gave me her Snow Leopard upgrade disc, which I ran and successfully upgraded the machine to Snow Leopard.
    Over the past few days I have noticed the machine running quite slow, so I ran Disk Utility-->Verify Disk, to which it said the drive was corrupted and needed the utility to run from the OS X disc. I don't have the original iMac discs, and the disc I used to upgrade the machine is no longer in my possession. I tried the OS X disc that came with my MBP, but it didn't work (being from a different machine).
    Short of getting the upgrade disc back, any other ideas on how I can run the disc utility or get another set of original discs?
    Thanks!

    Jason Kichen wrote:
    Short of getting the upgrade disc back, any other ideas ...
    you could give [AppleJack|http://applejack.sourceforge.net> a shot.
    Using AppleJack, you can repair your disk, repair permissions, validate the system's preference files, and get rid of possibly corrupted cache files. In most cases, these operations can help get your machine back on track. The important thing is that you don't need another startup disk with you. All you need to do is restart in Single User Mode (SUM), by holding down the command and s keys at startup, and then typing applejack, or applejack auto (which will run through all the tasks automatically), or applejack auto restart (which will also restart the computer automatically at the end of the process).
    JGG

  • Verify / Repair Disk Permissions Inquiry

    I recently had to do a full wipe of my system due to a massive permissions isssue. After cleaning the drive and reinstalling from "time machine" i became a lil paranoid and started checking the permissions every once in awhile.
    today i had an odd one pop up and i really don't know what to do.
    detail reads as follows:
    Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
    any input would be greatly appreciated.
    thank you.

    Most on here probably know more than me, but? I get the same message and also other suspicious events and each time i've ask for someone to advise why get message (or for that matter any time i question security on my mac) i receive same brush off response as you get. Don't worry about it? I'm worried about it and i think others should be worried also. I found the problem last night and when i tried to address it? my admin password (which i'd used each time i needed to do admin item) suddenly was changed. trying to change pw using mac osx install disc (freezes up) and ended up erasing hd and starting over.

  • Repair Disk Permissions: is it a safe operation ?

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

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

  • 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 greyed out?

    this may be a no-brainer, but i'm stumped. i recently installed Tiger onto one of my disk partitions (i'll refer to the partition as 'B") so that i could use DiskWarrior to repair the startup disk ("A").
    Prior to this, when I was running DW off the CD it was taking very long, appeared to hang on step 6 for 24 hours.
    the workaround worked great, repaired the disk in a matter of minutes.
    now however, i'm not sure if i've altered my system configuration.
    i was a bit freaked when after installing Tiger on the partition it restarted with the partition "B" as the startup. i changed the startup back to the original "A" and thought all was well.
    now however, i think i've noticed another change.
    in disk utility, the "repair disk" button is greyed out for "A"
    "A" shows Verify Disk Permissions, Repair Disk Permissions, and Verify Disk as options but NOT Repair Disk
    "B" however allows for all the options
    (Side note, I have 2 other partitions as well, now they only offer "Verify" and "Repair Disk", whereas I'm certain they used to allow for all options previously. Also, I've added an external HD during these changes. Maybe that's a factor?)
    Many thanks if anyone has any thoughts. This resource is truly indispensible!
    Dual 1.25 GHz Power PC G4, 2MB L3 Cache per processor, 1GB DDR SDRAM   Mac OS X (10.4.4)   also Rev B G3 iMac collecting dust

    I know DW takes a looooooong time to run. I've never seen it take 24hrs.
    DiskWarrior has an update for Tiger, You might check to see if you are using the newest version for DW.
    sometimes the computer sees whatever version your Mac has on its various drives and chooses the newest version to startup.
    I have 3 HD's an ext 40GB, a 120GB, and the original 80GB drive the Mac came with. OS9.2.2 on the 120GB, OSX 10.2.7 on the 40GB. and the main drive has OSX 10.3.9. I am sure Tiger works similar, the computer will make a choice to boot up with the newest OS, unless you tell it which OS to boot with. I may very well be wrong... just my observation from trial and error.
    I aim to remove my 10.2.7 when I get Tiger in next few months. consolidate my 9.2.2 & 10.3.9 on the 120GB and put Tiger brand new on the 80GB.
    So if things never work right, I can always reboot onto the old Panther.
    Of course when moving OSX system, always use Carbon Copy Cloner or SuperDuper, unless you like installing the OSX brand new everytime. OS9 is not as anal retentive.
    Verify/Repair Permissions is Very different from Verify/Repair Disk.
    your Disk Repair thing will never repair the startup/boot disk. If you are want here is good way to go...
    Boot off your OSX install discs. When it gets to the Install screen it asks what langauage you wish to install. Goto the File Menu and choose to Quit the installer. normally is an Option to use the Disk Utility. Then You should be able to Verify and Repair disk all you want on both Partitions without issue.
    Non-OSX disks will not allow Verify/Repair Permissions, but you can Verify/Repair Disk to hearts content on them.

  • Repair Disk is not successful

    While going through a verify/repair disk with OSX open, it said I needed minor repairs.
    I booted the OSX installation disk and ran verify/repair disk on my HD and drive. Both times the error said "1 HFS Volume Checked; 1 volume could not be repaired because of an error."
    I then restarted to sign back on and now nor my administrator and guest password will not work.
    I booted the OSX installation disk again to reset the password from there. It said it was successful.
    I then restarted to sign back in and the passwords still do not work.
    What should I do? If I reinstall the OSX all together should this fix the problem (I have everything backed up)? If so, is there ANY way I can access some files before doing so to make sure my backup is the latest (basically, sign back in before deciding to do so). Thank you in advance for your help!

    Hi Matt, and a warm welcome to the forums!
    Unfortunately, Disk Utility can't fix all that much, and the only other Apple Options are erasing the HD, or installing OSX to a second drive, then using Migration Assistant to move stuff over to the new HD.
    You must repair the HD, if Disk Utility or fsck should fail to repair it, your best bet is DiskWarrior from Alsoft, you'll need the CD to boot from...
    http://www.alsoft.com/DiskWarrior/
    There are other ways if you can't get DiskWarrior, let us know.

  • Verify/Repair permissions????

    Can anyone please explain to me what Verifying / Repairing Disk permissions actually does? I've heard people tell me it is like de-fragging in Windows....but I'm really curious what exactly is happening.
    I'd also like to know how often doing this is a good idea. Should I always verify AND repair? Which one first? Someone help me out...
    -justin

    Hi -justin!
    You'll find info here About Disk Utility's Repair Disk Permissions feature.
    I never Verify. I just Repair.
    I think Verify is a waste of time!
    It should be run before & after any upgrades, updates, or installation of applications or programs.
    ali b

  • Repair Disk Permissions Unavailable in Disk Utility

    I just went to repair the Disk Permissions on one of my 4 internal hard drive and the tabs for Verify & Repair Disk Permissions were grayed out. I checked the other internal hard drives as well as my external drives connected via SATA and Firewire and the tabs are all the same. The only drive that the tabs are available is my internal startup drive. I have a memory that these tabs to verify and repair have always been available on all drives - am I remembering incorrectly? Any ideas? Thanks.

    roam:
    Repair Permissions is only available to do, on the drive that you are booted into.
    I wondered about that, and before my previous post I tested it by launching DU while booted from my internal HDD and connected to an external FW HDD with two partitions, as well as to a USB HDD with my Time Machine backup. If I selected the FW HDD (Manufacturer ID) or either volume on it I could Verify or Repair Disk Permissions, as well as Verify or Repair Disk. It will Repair the TM backup, but not do anything with Disk Permissions. Of course, I am booted from Snow Leopard and did not test this while booted from an earlier OS, but, if I recall correctly, it worked the same way in Tiger and Panther.
    cornelius

  • Repair Disk Permissions with Lion

    Installed Lion two days ago and thought I would "Verify/Repair Disk Permissions" for the first time with Lion. But I'm getting the warning message:
    Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent” has been modified and will not be repaired.
    I tried "Repair" twice and got the exact same message both times. I'm not sure if this is serious or not, and can't say for certain if it wouldn't have happened a week ago or few weeks ago (it's been nearly two months since last "Verfiy/Repair"). Any lessons, tips, instructions will be appreciated.

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

Maybe you are looking for