A few weeks back, I was using my computer over the weekend. When I was done I did what I always do, I locked the screen and went to bed. When I came back and authenticated I was presented with the following pop-up
mac os needs to repair your library to run applications
What would ensure is another example of trial and error due to missing log messages. Read on to learn more!
As I mentioned, one morning I was presented with a message on my laptop. After authenticating like it had asked the message popped up again. I did this dozens of times before I realized that it was not going to go away. Given it took priority on my screen and I had no way of navigating anywhere else, I finally decided to hard reboot. When I logged back in, I was presented with what appeared to be a fresh install of mac os — the desktop was not the customized one I had created. In addition, the pop up message greeted me again — this was going to be fun.
Now I know what you must be thinking — it was something I installed or some change I made to the system. The thing was, I had not installed anything and I had not made any changes. The night before I was working on my homelab which required only a terminal window with SSH and a browser. While I would have loved to go check the logs, the pop up prevented me from doing anything on the same. Down the troubleshooting path I went:
- SMC reset — nope
- Single user mode — nope
- Recovery Mode with Disk Utility First Aid — nope
All the normal steps failed me so I decided to go back into Recovery Mode and see what Terminal had to say. I was able to properly navigate my home directory, but to my surprise 95% of my files and directories were owned by root and 5% were owned by “501”, which is my User ID number.
Note: I did check /etc/passwd to double-check it was my User ID number, but did not find the entry — then I realized mac os uses OpenDirectory instead.
Suspecting a permission issue, I was hoping to run the disk repair permissions option in Disk Utility, however I am running mac os Sierra and that feature has been removed. My only alternative was to reinstall mac os — so I did. Unfortunately, this did not fix the issue either — likely because the reinstall intentionally does not mess with existing home directories.
Running out of options, I decided to fix my home directory permissions from the Terminal application in Recovery Mode:
# chown -R <username> /Users/<username>
When I rebooted, I was happy to see that my profile was returned and the pop up was gone. I did not have a root cause, but at least my problems were solved — or so I thought. Everything appeared to be working properly, except my Outlook application. In my next post, I will cover the problems I had with Outlook as well as the solution.
© 2017, Steve Flanders. All rights reserved.