|
|
Wake up a MacBook that likes to sleep in
While early versions of FileVault may have been susceptible to the corruption you fear, you should be aware that Apple quietly introduced a new version of it in Mac OS X 10.4.7 last year. In earlier versions, the sparseimage's headers were written at the end of the file (they should've been called trailers then), so, if there was a problem writing or compressing the image, it could easily be corrupted. With the 10.4.7 update, they introduced a new version of sparse disk images so the headers are at the beginning (appropriately enough), making them much more resistant to failure. The catch is, if you created your FileVault with an earlier version, it continues to use the old, more fragile format. The solution is to just turn FileVault off, then turn it on again (probably using the secure erase option). The new FileVault will use the new format.
Wake up a MacBook that likes to sleep in
very interesting. unfortunately, it's still not enough. i corrupted a filevault image after one too many crashes on my macbook (all related to fast-user-switching and an external lcd it seems) just a couple of weeks ago.
Wake up a MacBook that likes to sleep in
DiskWarrior 4 claims to be able to repair corrupted FileVault images.
Wake up a MacBook that likes to sleep in
Interesting revelation about the improved sparseimage format -- does that apply to non-FileVault sparse images as well? I use several for things like financial info, etc. so I should convert them to the new format if so.
Wake up a MacBook that likes to sleep in
AFAIK, this applies to all encrypted sparse disk images. If you have such an image you created before 10.4.7, you might want to create a new one and copy everything over. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|