It sounds like a good idea in theory, but Apple’s FileVault sucks, and here’s why…

I installed the Mac OS X 10.4.7 update today (from 10.4.6) and it didn’t go so well (it’s not like I have some old/bunk Mac either, I have the newest quad processor PowerMac)… A reboot would give the system a kernel panic. Gee, cool… so I put the machine into firewire target disk mode and mount it as a volume from my laptop so I can pull some suspect extensions out of there. Okay, so far so good… ended up being some dependency issue with the USB driver, so I just yanked the kernel extension for the USB driver out of there for now.

Well guess what I found out? If you use your computer in firewire target disk mode and you go into your home directory, your FileVault image becomes corrupted. Hmmm… interesting… that means I just lost everything important (everything in my home directory). Would have been nice if someone tells you this (or better yet, just not let you do it). So now I have no home directory. :) Rad.

Thankfully, I just realized that the RAID mirror on my computer broke about a month ago and never rebuilt itself… so worst case scenario is I have to go back a month. Right now I’m disabling FileVault on the month-old volume (only another 1 1/2 hours to go). When that’s done, my home directory is going to be backed up to something (iPods are handy for more than just music). Then I can see about figuring out a way to “uncorrupt” my up to date FileVault image.

Just for the record, if anyone is using FileVault, disable it. If your single FileVault disk image gets corrupt (by whatever means), you just lost all your files.

I’m going to be one pissed off bitch if I end up having to go back a month…

Update

I just found this… I hope this helps (I’ll know in another hour or so I guess)…

http://docs.info.apple.com/article.html?artnum=25695