Skip to main content
Question

OS X need to repair your library

  • April 11, 2014
  • 11 replies
  • 60 views
T
Forum|alt.badge.img+9

Having errors with imaged 10.9.2 machines. It seems to be random for which users it does this do. One user will log in and get no errors at all. Next user will be prompted with the "OS X needs to repair your library folder". On those accounts if you go to "Go" hold option and click "Library" it takes you to /var/empty/Library. If you navigate to /Users/affectedUser/Library/ you see a bunch of the folders that are actually files. Any ideas?

Already had a look at this from https://jamfnation.jamfsoftware.com/discussion.html?id=10168 and ran the 

sudo update_dyld_shared_cache -root /

I'm thinking it was a bad .dmg w/ FUT but if thats the case why the randomness of it.

    11 replies

    bentoms
    Forum|alt.badge.img+35
    • bentoms
    • Hall of Fame
    • April 11, 2014

    We use FSTAB to mount a partition called /Users HD to /Users.

    When this mounting has failed, due to renaming a drive wrongly before imaging, I've seen the same error.

    I guess the OS cannot write to /Users.

    Does any of this correlate with your setup @tron_jones?

    T
    Forum|alt.badge.img+9
    • tron_jones
    • Author
    • Contributor
    • April 14, 2014

    No.

    It seems it is related to a bad .dmg that is using FUT. I am going through today and looking at the all the permissions and re-making some of the packages that FUT and FET. Hopefully that solves it.

    C
    Forum|alt.badge.img+7
    • CSHGreenwich
    • Contributor
    • April 14, 2014

    We were quickly upgrading and imaging over spring break and we had the same error. I noticed that only the test domain users that were logging on without adding a mobile account had the errors. the local account and domain users with mobile accounts had no errors. We set the account to never ask.. just to create a mobile account and have had no issues since then.

    C
    Forum|alt.badge.img+8

    Let us know what you find @tron_jones. I went through mine, but maybe I need to go through it again.

    T
    Forum|alt.badge.img+9
    • tron_jones
    • Author
    • Contributor
    • April 16, 2014

    @Chriskmpruitt
    This was fixed by going through and fixing permissions and rouge files that were using FUT and FET. After cleaning up the .dmg's we found a few that had keychain and system files left in the composer image. Cleaning those up and re-imaging 20 machines we haven't seen the error for repairing the library or keychain come back yet.

    T
    Forum|alt.badge.img+9
    • tron_jones
    • Author
    • Contributor
    • May 15, 2014

    @Chriskmpruitt
    Well after posting this we still experienced the issues with network users logging in and getting the revolving "Fix OSX library....". Just read the release notes of 10.9.3 and it looks like they might have addressed this.
    http://support.apple.com/kb/HT6228

    Improves reliability of network home directories

    Hope this is the answer.

    C
    Forum|alt.badge.img+8

    Holy Shark Repellent Batman! so far so good! We will be testing this for the next few days, I will let you know how it goes. But it looks like 10.9.3 might be the answer.

    J
    Forum|alt.badge.img+7
    • jake_snyder
    • Contributor
    • July 29, 2014

    Is anyone else still seeing this problem? I just joined a brand new imac with 10.9.4 to our AD domain with a brand new user account and we still are getting the "OS X needs to repair your library to run applications" error message. Any suggestions?

    P
    Forum|alt.badge.img+6
    • philcebutv
    • Contributor
    • February 1, 2016

    This is weird.

    I had setup 1 Yosemite iMac 10.10.5 and I got the error once wanted to know the fix before I deploy the iMac. Our users are logging in as their network accounts. It is completely random as the OP mentioned.

    donmontalvo
    Forum|alt.badge.img+36
    • donmontalvo
    • Hall of Fame
    • September 12, 2016

    Possible fix here.

    --https://donmontalvo.com
    M
    Forum|alt.badge.img+15
    • mhinsz
    • Contributor
    • December 20, 2016

    I ran into this issue today using Migration Assistant to move an AD user to another machine.

    Once I set AD user permissions to the user folder, it worked for me.

    sudo chown -R username:"DOMAINDomain Users" /Users/username

    Terms & ConditionsCookie settingsAccessibility statement