Community Page
- toxicsoftware.com Jump to website »
-
Subscribe -
Community
-
Top Commenters
-
Popular Threads
-
Recent Comments
- thank you for the information..
- I'm interested in migrating an EE site to WordPress, but I'm not as tech savvy as you. Do you ever do freelance jobs?
- just found your page, do you if there is a "generic" bluetooth app to remote control the nxt with a mac book? your software works only with space navigator?
- Three things: www.bitbucket.org causes a certificate problem because of the "www" subdomain. Pure python keychain access:...
- Hi. So can you please provide the the code for that application? Would be really appreciated!
Jump to original thread »
Sometime in the last couple of days (possibly the last week) the sparse image that FileVault stores my home directory within got corrupt. I noticed it yesterday when checking out Objective C files from subversion that ended up containing fragments of XML instead of the Objective-C source code th
... Continue reading »
2 years ago
We have a sparse image which after leaving mounted and experiencing a crash gives the error that it is a corrupted image and can't be mounted.
Is there any hope to recover this image?
Does anyone have any experience recovering in similar circumstances. Unfortunately we don't have a backup so this is problematic.
We read here: /filevault_corruption/
that you were able to copy the files from your sparse image to another. How do you do this? Our image is password protected (this is the whole point of doing it this way). So anyway we can copy the files from this corrupted image is ok.
Any suggestions how to do this? That is, save the files?
Thanks
Venu
vee308hotmail.com
2 years ago
2 years ago
http://ekettoz.blogspot.com/2007/02/filevault-h...
2 years ago
I just dont risk my data by using FileVault any more... But thanks for the link - hopefully it'll prove useful to others.
8 months ago
P.S.: it is a network account
8 months ago
5 months ago
<ol>
<li>I logged into the admin account I have had set up on my machine since the beginning so I could do some diagnostics</li>
<li>Immediately ran DiskWarrior, which reported that all the files could be recovered, but that it couldn't write the repaired directory, as it detected a media fault (I guess this means the damaged sparseimage acts the same as a damaged HD), so I should immediately copy the files to another location.</li>
<li>I quickly got out my portable backup FireWire drive, plugged it in and copied the files to the backup disk</li>
<li>Tried several times to copy the sparseimage file to another backup disk, so that I could go back if this whole process doesn't work</li>
<li>When Finder copy didn't work, I tried using SuperDuper! to copy the sparseimage, but that failed as well.</li>
<li>In frustration, I trashed the sparseimage, emptied the trash, then copied the recovered file structure from the DiskWarrior run into the Users folder.</li>
<li>Attempted to log on to my normal account, and got the same message, "You are unable to log in to the FileVault user account "bmc" at this time" with the second line "Logging in to the account failed because an error occurred."</li>
</ol>
Is that it? Is there any way to get the OS to "forget" about the FileVault status, and just deal with the recovered directory structure as if FileVault had never been turned on?
A couple of other pieces of information:
<ul>
<li>Running Leopard 10.5.6 now, but upgraded from Tiger.</li>
<li>FileVault was implemented in Tiger (the old version of FV), and I didn't do the right thing when I upgraded.</li>
<ol>
<li>I should have done a full backup.</li>
<li>I should have turned FV off before the drive got too full to do it.</li>
<li>I should have done a clean install and migrate, rather than upgrading over Tiger.</li>
</ol>
</ul>
Any assistance greatfully appreciated! This is both painful, and time consuming!
5 months ago
I haven't used FileVault in years - since this blog post actually. Wish I could help but really - might be time to create a new user account and swap your files manually? I don't know.
Sorry.