FireWolf Pl.

A Place of Freedom

@FireWolf7 years ago

OS X OS X El Capitan

RepairPermissions V2.0 – With repairing permissions on OS X El Capitan's whole disk supported

RepairPermissions V2.x has been deprecated.

Please use RepairPermission V3 instead.

V1.0 was not released publicly and was integrated in my FireWolf OS X PE because the only job it did was running

diskutil repairPermissions.

However, repairPermissions verb was discarded in the new DiskManagement.framework of OS X El Capitan.

So this is a new version of RepairPermissions command line tool.



RepairPermissions is an easy command line tool to repair the permissions of an OS X system volume.


Update Logs:


Resolve an issue that RepairPermissions may not function properly under OS X Mavericks.


1. Repairing permissions on OS X El Capitan’s whole disk is now supported.

2. Repairing permissions under normal OS X, OS X Single-user mode, OS X Recovery is fully supported.


Supported OS X:

OS X Mavericks (10.9.x)

OS X Yosemite (10.10.x)

OS X El Capitan (10.11.x)



RepairPermissions targetVolume

where targetVolume is a valid mount point of a system partition.



0. RepairPermissions should be placed at /usr/local/bin if you want to use RepairPermissions directly from OS X’ Terminal.

1. You can ONLY repair the permissions on the current root volume if RepairPermissions is used in single-user mode.

2. TABLES (You can ONLY repair the permissions on OS X El Capitan under OS X El Capitan.)

















RepairPermissions V2.0 – With repairing permissions on OS X El Capitan's whole disk supported

  1. Vincent

    Can you explain how this command works?
    I thought in El Capitan Permissions can’t be corrected due to limitations with rootless and System Integrity Protection.

    1. FireWolf Write

      SIP protects the system from being modified by root.

      But my command line will directly repair permissions for the whole partition even though Apple has removed repairing permissions function in Disk

      1. Vincent

        Ok. Thanks.
        But how does your command do that?
        Does it call a function in DiskManagement.framework that by design can bypass SIP regardless of rootless?

          1. Desmond Foulger

            Respectfully, (of course) FireWolf needs to come out of hibernation in order to update repair permissions script and disk utility (old) to work with macOS Sierra. Also PE V7.0.x Please do this for us FireWolf Cubs (Pretty Please)

  2. UnknownUnknownUnknownUnknown

    I *really* want to repair permissions in El Capitan, so thanks for your help.
    The name of my boot volume is DLB TerraByter x3
    However, after I drag your executible file to the Terminal’s shell window and type:
    RepairPermissions /Volumes/TerraByter x3, I get “Command not found.”
    –Any help?
    Thx for all you do, Dave B

    1. FireWolf Write

      Hi Dave,

      For instance, you have put the RepairPermissions command line tool on your Desktop. Then what you should do is opening the terminal and typing the following commands.

      cd ~/Desktop
      ./RepairPermissions /

      OR cd ~/Desktop
      ./RepairPermissions /Volumes/DLB TerraByter x3

      (P.S the reason why you have to replace the ” ” with ” ” is due to the UNIX terminal rule.)
      (P.P.S You can also use / to represent your current boot partition, because / in OS X means the root volume.)

      Feel free to leave comments if you have any further questions.


  3. lee

    Hi, please can you help me? i want to repair permissions for /usr/lib folder on my mac so i can write files into this folder. in El Capitan i don’t have permission. any help would be greatly appreciated. could you break it down in an easy format for me to understand. thanks Lee

    1. FireWolf Write

      Hi Lee,

      You can find the usage information at any time by typing RepairPermissions help in the terminal.

      Basically my command line tool only requires an argument which is a valid mounting point of a OS X partition. Well there is a “shoutcut” that you can use / to represent your current boot volume.

      To be more specific, supposed your OS X El Capitan’s startup disk name is “Macintosh HD”, you can use either “RepairPermissions /Volumes/Macintosh HD” or “RepairPermissions /” to repair permissions for your entire system partition under OS X El Capitan.

      Feel free to leave comments if you have any further question.


  4. Manfred

    hi, I really need this. but my terminal can’t open because of my installation of homebrew. I think it broke something. So I run your tool in recovery mode. it failed with ‘path not accessible error’

  5. Jack

    Thanks for this nice GUI software. Im running Repair Permissions as I write this.

    1. “Status” currently says “Repairing permissions…” but if I mouse over the window the beachball appears. Also, if I click-hold the KCPM Utility icon in the dock, “Application not responding” is written. So Im not sure if it is working or not.

    2. When I open the main Window of KCPM Utility Pro –> Maintenance, 2 boxes are checked by default. Is this done intentionally? I hope to Repair Permissions in El Capitan, but was I supposed to leave the “Rebuild System and kexts…” box checked too?


    1. FireWolf Write

      Hi Jack,

      For the first question, actually it is working even though the beachball is spinning. Don’t worry about that. I didn’t enable the multi-threading due to the safety. You know some people may press the Execute button twice and therefore submit the duplicate operations.

      For the second question, yes these two check boxes are selected by default. Because it is recommended to repair permissions and rebuild caches after each kext installation no matter which version of OS X you are using. In addition, you also don’t have to worry about the operation sequence when you selected these two check boxes as repairing permissions will always be executed before rebuilding caches.


      1. Jack

        Thanks for your kind reply. Using the GUI software with just “Repair Permissions” selected, running for 1 hour nothing seemed to be happening (no feedback on progress either) so I quit and installed the command line version. Then I ran the command line version in Single-user mode for a couple of hours and it hung too. SO I tried the command line version in Terminal in Regular mode for 8 hours and it hung (also with no messages on progress). Actually, it might have done something but there was no feedback so I assumed that it hung and I control-c’d out of it. Can you possibly consider adding a verbose mode so we can see if something is happening at all? Thanks!

  6. Joon Kim

    Really thanks for this.
    I resolved El Capitan problem which plagued me for 2 full days.
    I don’t understand why they removed this util from El Capitan.

    Here is my problem solved after running it.
    -All hard disks except system hard disk show only blank icons for all folders.
    -If I click any folder, it is empty.
    -But files are all OK when I see on Terminal or even on remote PC through Samba. This is only Finder problem.

  7. kinobijei

    Hey guys, I’m trying to repair disk permissions on an external disk NTFS formatted.
    I’ve disabled SIP and mounted the disk creating an antry in the file /etc/fstab, not using any thirdy party solution to get NTFS writable.
    I’m getting the following error as root when trying to repair disk through the above mentioned utility:

    RepairPermissions /Volumes/Elements/
    Code 1.
    Target volume may not be a valid system partition.

    Do you see any solution?


  8. Jeff

    Hi FireWolf,

    I know Apple make a command line tool named “repair_packages” and I’d like to know whether your this tool run it? I checked this and I saw “repair_packages” via running your “repairpermissions-v2-0-cli”…

    sudo /usr/libexec/repair_packages –repair –standard-pkgs –volume /

    Did your CLI use the command above?


  9. Desmond Foulger

    Thank you so much for this extremely useful gem. I have ALWAYS repaired permissions on every computer I upgrade or look at (I’m a Mac technician) and this, together with Diskwarrior has always got rid of 99% of pre-install problems, especially before system upgrades. Have you noticed that the printer permissions are ALWAYS wrong?