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


Click here to return to the 'Some possible fixes if FileVault goes awry' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Some possible fixes if FileVault goes awry
Authored by: mike666 on Mar 30, '05 05:54:20AM
Ah, I'm getting a better picture of this.

Close, Safar, but what actually happens is that when logged in, the user's home folder is renamed to .shortusername with the unmodified sparseimage inside it and then a new home folder is created and the mounted sparseimage is mapped to that. When the user logs out, all that reverses itself. At least this is what happens under 10.3.8. Since the logged-in folder structure was what I saw when viewing the contents of /Users while logged in as the other account on the machine - and the FileVault protected account wasn't logged in - something must've hung up during the closing process during the last logout of the FileVault protected account. My initial fix of renaming the folders would've worked had the sparseimage itself not been damaged. My client however, asked me to restore the data to a non-FileVault protected account - he was understandably leary of trusting FileVault again! I didn't go into it in the article, but I also received the machine (a TiPB 500) with outdated firmware, which might have actually been responsible for the whole FileVault debacle. It also took some doing, but I made sure the firmware was updated before I did any troubleshooting of the login problem.

[ Reply to This | # ]