Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

A fix for a FileVault home directory repair issue System
Apple's Knowledge Base article on How to verify or repair a home directory image didn't work for me.

When I clicked repair at step 12, Disk Utilty was not able to repair the volume because of permission problems. After some research, I found the problem. The FileVault aegim file is not owned by the account you are logged in as to effect the repair, so when you attempt to use Disk Utility to repair it, it can't. To work around this issue, I added write permission using Terminal:
% sudo chmod g+w accountname.sparseimage 
Run this in the directory of the user you want to repair, and replace accountname with the user's short username. This will usually work, as all users belong to the group staff. You also need to do this command on the directory of the user's home directory
%sudo chmod g+w /Users/accountname
Now you can run Disk Utility to repair the image successfully. Remember to change the permissions back afterwards:
%sudo chmod g-w accountname.sparseimage
%sudo chmod g-w /Users/accountname
[robg adds: I haven't tested this one, as I'm still not using FileVault...]
  • Currently 1.00 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (1 vote cast)

A fix for a FileVault home directory repair issue | 4 comments | Create New Account
Click here to return to the 'A fix for a FileVault home directory repair issue' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Each user in Tiger has its own private group
Authored by: hayne on Jan 20, '06 09:34:38AM
The article says "users belong to the group staff". That was true in some earlier versions of OS X and for user accounts carried over from these earlier versions, but it isn't true for user accounts created in Tiger. (I don't recall but I think it wasn't true for Panther either.) On Tiger, each user belongs to its own private group.

% id fred
uid=502(fred) gid=502(fred) groups=502(fred)
This means that the 'chmod g+w' specified in the article will not be sufficient to give write permission to another user. Instead it likely would be necessary to use 'chmod a+w' to give all users write permission.

[ Reply to This | # ]
Each user in Tiger has its own private group
Authored by: barefootguru on Jan 21, '06 10:59:44AM

'chmod o+rwx' is more specific than 'all', and then you can use 'chmod o=' when finished.

Alternatively, just enable the root user and use the root account to carry out the repair. Remember to disable root again when finished.

[ Reply to This | # ]
A fix for a FileVault home directory repair issue
Authored by: bitwise on Jan 20, '06 03:33:16PM

I think this issue does not typically present itself because the default to ignore ownership is set for the sparseimages when viewed from outside the account. But if this is changed by mounting and unchecking the checkbox in the image's info window or otherwise, then this hint will be necessary. Or you could recheck the check box to ignore ownership. Also consider that if for some reason other does not have read permission, you will not even see the mounted image in the finder. You can still see it in terminal in the Volumes directory though.

[ Reply to This | # ]
A fix for a FileVault home directory repair issue
Authored by: ekettoz on Feb 27, '07 06:31:05AM
I wrote up a tutorial on how to fix this issue without having to tweak ownership or read/write/execution rights. Hope it helps you guys:

[ Reply to This | # ]