Corrupt FileVault Sparsebundle

Hello,
I'm running into some mighty big issues with FileVault, and would deeply appreciate any help.
(a) It all started when I brought my macbook out of sleep mode and tried accessing my Yahoo mail. Safari came up with an error "Safari can't establish a secure connection to the server". Got the same issue for all https sites. On accessing mail, it said no account configured (though I have been using a couple of them for a couple of years now). iPhoto said no file exists. I got worried that I had had a virus intrusion and ran Sophos anti-virus, but quit it half-way through and rebooted the macbook.
(b) After reboot, the macbook did not allow me to login. It gives me an error "FileVault Protected-home folder is damaged. Press OK to repair or Cancel to login as a different user" On pressing OK, it said Login Failed.
(c) Called Apple Support (India), they tried a couple of hardware resets (Not sure now but I think he tried to reset the PRAM and something else in the boot routine to factory defaults). That did not do much good, so he tried fsck (in single-user mode from the root; since I could not login). That did not do any good either so he directed me to the nearest Apple store.
(d) The apple store pretty much told me that the data's gone corrupt, but helped me install a root user (I just had one user initially; at the apple store, they used the install disk to boot and then added a root user). After logging in through the root, saw that the Users folder in the Macintosh HD had a sparsebundle file (myoriginalusername.sparsebundle; this is about 23.9 GB in size, I estimate I would've had about 45-50 GB of data)
(e) Read through in the discussions forum and have tried the following steps to recover from the sparsebundle:
i. Double-clicked on the sparsebundle file. It asked for password, gave the old password which was accepted but came up with an error "No mountable file systems"
ii. Tried to open the file with disk utility. It opened up (showed on the right side). On verifying with Disk Utility, it comes up with an "Invalid B-tree node size" (I understand that this is one of the worst that can happen to mac users; I'm keeping my fingers crossed)
iii. Took a backup of the sparsebundle. Created a blank disk image with the sparse format, copied the myoriginalusername.sparsebundle file to the disk image. Ran the data rescue (Demo version) quick and deep scans on the disk image. The data rescue scan did produce some files, but they were hardly recognizable.
iv. Created a new user (so that there are 3 users now; myoriginalusername, root & newusername). Copied the disk image created in iii above to the home folder of the new user created. Restarted in safe mode and logged in as the new user. Tried mounting the disk there and ran disk utility. Had the same issues.
I've pretty much run out of things to do to recover this one. Any help would be great. Please note that the sparsebundle shows a folder Bands (containing plain text files of 8MB each), and 3 files - info.plist, info.bckup and Token.

Your sparse bundle is likely toast, but this is worth a read: http://www.thexlab.com/faqs/fixfilevault.html
the sparsebundle shows a folder Bands (containing plain text files of 8MB each), and 3 files - info.plist, info.bckup and Token.
Yes, that's how sparse bundles are constructed. There may be many thousands of the "bands." That's where the encrypted data is. The advantage is, only the changed bands need to be backed-up.

Similar Messages

Can't copy some files from FileVault Sparsebundle in Time Machine backup

I've got filevault turned on for my mac Mac Mini (10.6.2). I'm using Time Machine to back up to a firewire drive. There's plenty of space - my Mini hd has 250 Gb of 500 used, and I'm backing up to a 750Gb partition on the external drive. The initial backup went OK, and when I logged out it backed up my filevault-protected home directory. When I logged back in, I was able to browse the Backups.backupdb on the external drive, go to the users directory, and open the sparsebundle that was my filevault-protected home directory (after entering the password). I can browse through this backup of my home directory. However, when I try copying files from the backup of the home directory, I get an error:
The Finder can't complete the operation because some data in "(filename)" can't be read or written. (Error code -36).
I get this error for some files, but not all of them. I've tried running BatChmod to reset permissions on all files in my home directory, and then erasing the backup drive and having Time Machine recreate the backup. However I'm still having this problem.
I have also tried restoring the entire hard drive (to a 3rd external HD) by booting from the 10.6 DVD and going through the full-restore process. All of my files are fine when I restore using this method.
Is there something I should do so that I can restore individual files from the backup of my filevault sparsebundle? It is extremly inconvenient to have to do a full hard drive restore if all I want is a file or two, and of course if the motherboard on my mini dies and I can't get a close enough replacement computer, then I could really be up a creek.
Thanks,
John F
New York

feinberj wrote:
I've got filevault turned on for my mac Mac Mini (10.6.2). I'm using Time Machine to back up to a firewire drive. There's plenty of space - my Mini hd has 250 Gb of 500 used, and I'm backing up to a 750Gb partition on the external drive. The initial backup went OK, and when I logged out it backed up my filevault-protected home directory. When I logged back in, I was able to browse the Backups.backupdb on the external drive, go to the users directory, and open the sparsebundle that was my filevault-protected home directory (after entering the password). I can browse through this backup of my home directory. However, when I try copying files from the backup of the home directory, I get an error:
The Finder can't complete the operation because some data in "(filename)" can't be read or written. (Error code -36).
I get this error for some files, but not all of them. I've tried running BatChmod to reset permissions on all files in my home directory, and then erasing the backup drive and having Time Machine recreate the backup. However I'm still having this problem.
I have also tried restoring the entire hard drive (to a 3rd external HD) by booting from the 10.6 DVD and going through the full-restore process. All of my files are fine when I restore using this method.
Is there something I should do so that I can restore individual files from the backup of my filevault sparsebundle?
Don't try to restore files individually by hand using finder. TM backups are protected by very restrictive ACLs and are not designed to be accessed that way.
you can restore the whole sparse bundle with the home directory from TM interface. you should be logged in as a different user when you do this. the easiest is to be logged in as root so as not to deal with any permissions issues.
another thing you might try is doing it from command line instead of finder. this is also not the designed way but might work where finder copy doesn't.
to do this run the following terminal command after you mount the sparse bundle with backups of the home directory
ditto --noacl path/to/source/file /path/to/target/directory
here path/to/source file is the path to the file in the sparse bundle you want to restore and path/to target directory is the path to the folder where you want to copy it to. an easy way to get the path to an item is to drag that item to the terminal window. make sure that you have all the spaces correctly in the command.
It is extremly inconvenient to have to do a full hard drive restore if all I want is a file or two, and of course if the motherboard on my mini dies and I can't get a close enough replacement computer, then I could really be up a creek.
Thanks,
John F
New York

Chmod in mounted FileVault sparsebundle does not work?

I wanted to change my UID to match the NFS server, so all permissions & ownerships are right. So, I followed this stuff: http://www.inteller.net/notes/change-user-id-on-snow-leopard But this did not take into account users that had FileVault turned on, and I discovered this afterwards, naturally.
So, after completing the above (but not logging back in as my regular user, ie. still logged in as root) I mounted the FileVault sparsebundle, opened a shell and tried to chown all files in the mounted volume.
This did, however, not work. The chown exited with status 0 (meaning OK) and no error message, but doing a ls -nl showed that the ownership was still my old 501, rather than the new 1000 (I did "chown -R 1000 Documents", for example).
I tried "touch test", and it worked. So I had write permissions to the volume.
So I tried "su - username". And then ls -nl. Viola! The uid's where all 1000! So, exit, back to root. Then ls -nl again. Now all uid was back to 501!?
Then I unmounted the volumed, log out and log in as the user, but this created problems since all files were owned by 501. So I tried "sudo find -xL . -uid 501 -exec chown 1000 {} \;". Now all files seemed to be OK, log out, log back in, works.
So, I fixed the problem. But I'm still very curious about this behaviour. Why could I not change the ownerchip, when logged in as root, on a mounted FileVault sparsebundle.
Any ideas?

I had this same problem, went through same process and got same result. Then tried disk on another Macbook Pro, ran Repair in disk utilities and this time was told disk was not repairable and that I had to reformat it. Based on a recommendation in another forum, I bought DiskWarrior. DiskWarrior was able to repair the drive, which was a huge relief since I had irreplaceable files on that drive (thought it was safe because it was RAID).
I am now copying files off that drive in case this happens again. I have not turned the drive off yet, just in case it doesn't come back online again. I recommend trying DiskWarrior if you're in this situation.

How to repair a filevault sparsebundle with disk utility?

I've been experiencing some oddness with my filevault home directory so I wanted to drop into disk utility and run a check/repair on it. The odd thing is, when I log out and into another account, the sparsebundle says 0k in the finder, and appears to be a directory. When I sudo to cd into the directory, it appears to work, but I remain in /Users/username. When I drag the sparsebundle into disk utility, it appears in the bar on the left side of the screen, but clicking repair or verify causes the progress bar to activate for a split second then stop with no error message. Trying to mount the sparsebundle yields a "No supported socket" message.
I am able to log into the account. When I do that, in /users/.username directory, I can see the sparsebundle with its true size, 35 gigabytes.
I used to repair sparseimages; is the described behavior "normal" for sparse bundles and if so, is there a way to get them repaired in disk utility? Or is this odd behavior on the part of this particular sparse bundle?

Well a bundle and a disk image are both, likewise, "very different things" than actual independent storage devices, but disk utility is able to reason out that it needs to ask for the password for the disk image and open it in order to repair it. There's no reason why it couldn't be as bright when it comes to handling a sparseimage.
You are correct that mounting it first with a terminal command (sudo hdiutil mount -nomount -readwrite /path/to/sparseimage) causes it to be repairable in disk utility. Disk utility can figure out by itself that it needs to open the disk image when you repair a disk image, but apparently not with a sparsebundle. I disagree with your tone above that implies that somehow one would not expect disk utility to function robustly and be actually capable of repairing Apple file system-based virtual disk images (whether a single file or in a directory format, doesnt matter), and that one should be expected to dig up a terminal command and mount it manually before being able to tinker with it. That's not reasonable to expect of the user for a routine task such as repairing a disk image.
However on doing so, disk utility can repair the disk.
See:
http://blog.hardmac.com/archives/how-i-saved-my-corrupted-time-machine-sparsebun dle-image

Exclude FileVaults sparsebundle from backup

Hello,
I'm trying to configure Time Machine to backup my Mac on system level without my home folder. The problem is, that my home folder is encrypted via FileVault and regardless of what I'm doing, Time Machine tries to backup FileVault's sparsebundle every time I logging me out. I have tried to add "/Users" or "/Users/.<username>" to the exclude list or edit Time Machine's configuration file manually but nothing helps.
How can I prevent Time Machine from backing up this file?
Thanks and greets,
Jay2Cee

Jay2Cee wrote:
V.K. wrote:
Jay2Cee wrote:
My system files are the only one I really need to backup and I want to use the build in tool for this purpose. But even if I exclude my home directory from the backup in TM settings, at logout it really backups the FV sparse bundle and I haven't found a way to stopping it from doing that.
why do you think that? how did you check? it certainly should not do that. it doesn't back up the sparse bundle when I test it.
The backup takes a very long time
that doesn't mean anything
and the result is big sparse image file in the backup
and that does not mean anything either. it simply reuses the old existing backup of the sparse bundle and hard links to that. the only true test is to delete all backups of the sparse bundle. then log in/out of the filevaulted account and see if the sparse bundle is really being backed up. my bet it isn't.
deleting backups should ONLY be done from TM interface. enter TM, scroll back in time and select the sparse bundle in any backup. then click on the "gears" action button in finder's toolbar and select "delete all backups of ..."

Help. Accidentally deleted filevault sparsebundle image..

Hi all,
I did an incredibly stupid thing today. I went an deleted (dragged to the trash, but did not empty it) the filevault sparse bundle image in my user directory and went and shutdown my Macbook. After a reboot, I could not log in.
Is there a way to recover from this situation?
If you want to know how I got myself in this mess, I was trying to make space on my macbook and found a 44GB file. I didn't know what it was and just tried to drag it to the trash to see if anything bad would happen. After moving to trash, things seemed ok, so I shutdown the machine for a while. So that's how it happened. Now I'm kicking myself.
Thanks for any help.
Nik.

Nik Hisham wrote:
Hi VK,
Thank you for pointing me in the right direction. I logged in as Root, opened a Terminal window and found the sparsebundle image sitting in /.Trashes. I just did a mv to move it back to my user directory. I was able to immediately log back on using my user id.
glad you've fixed it.
It was a good thing I didn't empty the trash after moving the image there.
actually you would not have been able to empty trash because the disk image was in use at the moment.
Nik.

FileVault sparsebundles lost converting to Lion

I had an external disk doing TimeMachine backups of snow leopard home directories encrypted with FileVault (ie into sparse bundles). I could get to the disk and extracted most of what I needed from a computer running Lion, so I know they were good when the left 10.6. However, when I started to use the disk as a Time Machine disk on Lion, it converted all my sparse bundles to directories (not sparse bundles) with no permissions (probably still encrypted, too).
$ ls -l
total 0
dr-x------+ 3 503 staff 102 Dec 16 2009 erik
$ sudo chmod g+rwx erik/
chmod: Unable to change file mode on erik/: Operation not permitted
$ sudo chown kastman erik/
chown: erik/: Operation not permitted
I tried to chown and chmod, but get an operation not permitted. This seems like a horrible design flaw, but I can't find any other help toipics where this has happened.I'm currently verifying permissions in case there was something that broke, but I'm lost on how to recover the bundles now. Any ideas to get my backups back?
Erik

Permissions finished verifying correctly, so that's not it. Anyone have any ideas? Otherwise I'll open a ticket with Apple proper. Thanks in advance,
Erik

How can i delete a corrupted sparsebundle file

My TimeCapsule sparsebundle file is corrupt and cannot be opened by TimeMachine anymore. However I cannot delete it either, error message: "The process could not be completed as the object "bands" is in use." (my translation from my German original: "Der Vorgang konnte nicht abgeschlossen werden, da das Objekt "bands" in Verwendung ist")
ANY IDEA HOW I CAN DELETE THAT SPARSEBUNDLE WITHOUT FORMATTING EVERYTHING?
Maybe you need the whole story to come up with some good ideas, this is how it came:
- I bought a new 500GB TimeCapsule and tried to do a first backup. It ran the whole night through and wasnt done the next morning. However I had to leave to work and had to cancel it at 80% or so.
- I tried it again on the weekend, but hat to cancel again after dozens of hours of slow backup without success. Finally the sparsebundle file had grown to several hundred GB and I thought I better delete it before trying to backup again.
- Hence: I picked the file and delete, confirmed that it would be deleted straight away (without being moved to the basket before), it started deleting but stopped half way.
- SO NOW: i can neither use the file through timemachine, nor get rid of the file to start timemachine again.
Thanks in advance for your ideas...

I tried downgrading the firmware back to 7.3 and that didn't work for me either, neither did resetting the Time Capsule.
It ended up that my sparsebundle was in indeed corrupted (for the 2nd time now) which is completely crazy to me!...
I did find out *WHY my sparsebundle kept getting corrupted*:
I learned that when time machine is turned on, if the computer goes to sleep, about 50% of the time, that will "corrupt" the sparsebundle!
What I had to do last night was delete my sparsebundle (again) and then do the dreaded, long "first backup" all over (overnight).
I made a point to go to the "*energy saver*" on my preferences to change the settings on it so that it wouldn't put the MacBook to sleep (both on the battery and power options) so that my sparsebundle won't get corrupted again!
This was really frustrating, and that little piece of information should be included with the Time Capsule for consumers so that they can avoid the frustrations that we've all apparently been having. I'm suprised at Apple, and a little disappointed in all of the time that I spent/lost dealing with the Time Machine and Time Capsule.
Hope this helps :0l

Bootstrapper Crash Need to Backup FileVault Home Folder Before Rebuilding

Bottom Line (yes repeated at the bottom ;-))
How do I mount the sparse bundle (FileVault created) from the limited resources available on the OS X install DVD so I can check the integrity of contents, or even just copy the contents unencrypted?
I may just take this into the Genius bar, assuming the correct Evil Genius is available, but if I can get help here it will save me the drive across town.
Background:
Power fault and a hard shutdown, now my iMac won't boot.
Backup of Home folder is about 3 months old using Backup utility (no lectures please, long story)
I would like to backup what I have before doing anything dramatic (like erasing the drive and starting over)
I am using FileVault, which I suspect will complicate things (albeit the backup I do have is unencrypted and in the safe) and was able to copy most (but not all) of the sparse bundle.
I.e., I believe both the system files and my home folder have issues.
I would be satisfied with even an unencrypted copy of the files in the home folder (FileVault sparse bundle), but I am having trouble backing anything up (I/O error, which may mean that a band inside the sparse bundle is corrupted as well).
Possibly Relevant Details:
Single User Mode (i.e., via Command-S) does not reach prompt
Instead I see several "disk0s2: I/O error." with the error details followed by "The system bootstrapper has crashed"
It does point to the specific file issues, but at this point I am less concerned with the system files than I am with the Users home folders (mine and the kids)
Using the OS X DVD and launching Disk Utility the repair disk does not work (even when repeated, which has worked on other disks before).
Invalid sibling link on Verify followed by Invalid node structure (fails trying to rebuilding the catalog b-tree... invalid node structure and invalid record count repeated several times followed by invalid key length, then repair gives up.
Disk Utility unmounts the volume and won't let it re-mount.
Managed to re-mount by forcing the drive to be the start-up disk (Power On with Option key) and then re-started again from the DVD.
Could not figure out how to force the mount from the Terminal.
Again, running from the DVD and then using Terminal I can see the volume (../../../Volumes/Macintosh\ HD) and what appears to be the contents.
On a whim I tried to copy the Users folder to an external drive and then saw the error message about the FileVaulted sparse bundle (file .mtkessel in Users)
Copying the kids home folders this way worked, so the only problem appears to be my home folder (which is a sparse bundle).
Specifically, the "I/O Error" reported by cp is in .mtkessel/mtkessel.sparsebundle/bands/1 and 10... all of the other bands and the related Info and token objects copy just fine. I suppose it is possible that those bands are ones slated for reclamation at the next logout, but I can't be sure.
So I suppose the question is how do I mount the sparse bundle (FileVault created) from the limited resources available on the OS X install DVD so I can check the integrity of contents, or even just copy the contents unencrypted?
Thanks in advance on this ugly problem...
mk

It took many hours to copy the FileVault sparsebundle (both size and device issues I suppose), but I managed to re-assemble it, including the "Rescued Items"; I just used the unix cp -R on the sparsebundle file to force the copy to report the I/O errors... about a dozen or so of the 9000+ bands are damaged.
Could not really tell if anything other than the "Rescued Items" were missing since bands can be deleted during normal use.
I then attached the sparsebundle (which is encrypted) with a shadow (i.e., this sparsebundle is not mountable)
This is the command I used from the directory containing the COPY of the sparsebundle.
hdiutil attach -encryption -noverify -ignorebadchecksums -nomount mtkessel.sparsebundle -shadow bundle.shadow
I am not entirely sure, but the shadow option allows read-only behaviors on the device to be circumvented by allowing write through the shadow...
Enter the password and then I had he "device" appeared in the dropdown menu in DW and then I was able to re-build it.
Then in Preview I was able to see a fully mounted device from which I have started copying. The damage was "easily corrected" according to DW. It may take several hours to copy as well (this time probably due to the decryption as it copies)
I am starting to experiment with the Mail import features to see if I can recover the e-mails... my first attempts of importing from both Apple mailboxes as well as mbox format did not work. And, simply copying the emlx files into the mbox destinations does not work... The items simply don't show up in Mail... I am sure I will figure it out eventually, but any advice on importing the emlx files would be much appreciated!
mk

Time Machine error -1, cannot access sparsebundle (but not a NAS or WD problem)

Hello, this is my first post here, so I'll try to make it a good one!
I've been wrestling with this problem ever since I bought my Core i7 iMac (SSD + 1TB HD) over a year ago. I have not gotten Time Machine to work during that whole time. Well, I got it to work backing up directly to my internal HD, but that was just a test; it's not what I want. So let me describe this in the most clear and consise way I can:
I want the Time Machine disk to be my Synology NAS. I've configured a share on it correctly. I have an older iMac running SnowLeopard backing up to the same share on the NAS with TimeMachine successfully. But, my iMac won't do it. Whether I create the sparsebundle manually, or I let TimeMachine create it, it always gives the same "error -1". I wrote a more detailed account of my symptoms here (my message is the reply), when I thought this was a NAS-specific issue.
New development: This is not a NAS issue. I found that out by trying an experiment:
First, I tried to back up my SSD using Time Machine to my internal 1TB disk - I selected the "1 TB Secondary Disk" as the Time Machine disk. I initiated the backup, and it worked fine, putting the time machine backup in the "Backups.backupsdb" directory structure at the root of the drive. I then turned off Time Machine and "removed" the 1TB as my backup disk.
Then, I created a sparsebundle at the root of the drive using this command:
hdiutil create -size 150g -fs HFS+J -volname "Time Machine" NAME_xxxxxxxxxxxx.sparsebundle
(where the "xxxxxxxxxxxx" is my ethernet MAC address). I then selected the "1 TB Secondary Disk" as the Time Machine disk again. Time Machine found my sparsebundle and started working with it... and got "error -1"! So even on a local drive, when Time Machine tries to use a sparsebundle for backing up, it still doesn't work.
Now, I have the console log entries that were written during the Time Machine backup attempt:
1/1/13 12:53:59.511 PM com.apple.backupd[4460]: Starting manual backup
1/1/13 12:54:00.780 PM com.apple.backupd[4460]: Renaming /Volumes/1 TB Secondary Disk/NAME_3c07540fdd8c.sparsebundle to /Volumes/1 TB Secondary Disk/iMac.sparsebundle
1/1/13 12:54:00.871 PM com.apple.backupd[4460]: detach: could not open /dev/disk4
1/1/13 12:54:01.260 PM com.apple.backupd[4460]: Resizing backup disk image from 161.06 GB to 999.76 GB
1/1/13 12:54:02.940 PM com.apple.backupd[4460]: Waiting 60 seconds and trying again.
1/1/13 12:55:03.378 PM com.apple.backupd[4460]: Resizing backup disk image from 161.06 GB to 999.76 GB
1/1/13 12:55:06.013 PM com.apple.backupd[4460]: Waiting 60 seconds and trying again.
1/1/13 12:56:06.619 PM com.apple.backupd[4460]: Resizing backup disk image from 161.06 GB to 999.76 GB
1/1/13 12:56:09.255 PM com.apple.backupd[4460]: Giving up after 3 retries.
1/1/13 12:56:19.263 PM com.apple.backupd[4460]: Backup failed with error: 21
1/1/13 12:56:19.265 PM com.apple.backupd[4460]: [SnapshotUtilities mountPointForVolumeRef] FSGetVolumeInfo returned: -35
1/1/13 12:56:19.265 PM com.apple.backupd[4460]: Failed to eject volume (null) (FSVolumeRefNum: 0; status: -35; dissenting pid: -1)
1/1/13 12:56:19.265 PM com.apple.backupd[4460]: Failed to eject Time Machine disk image: /Volumes/1 TB Secondary Disk/iMac.sparsebundle
So, here I see it tries to resize the sparsebundle to the full volume size, and fails. I don't think I want it to do this resize, because I don't want it to fill up my whole NAS share. I searched and found this post, which specifies how to set the permissions in the sparsebundle such that it won't be resized. I followed those instructions with a new sparsebundle, and see the same problem... tries to resize, and fails.
I do not have Western Digital software installed and never have.
I've tried everything on this page.
It seems like the attempt to resize is corrupting the sparsebundle. Before starting the backup, I can mount the sparsebundle and manually copy files to it. After attempting the backup, I can mount the sparsebundle, but I cannot copy anything to it manually. Note that I can mount the sparsebundle that the MacBook Pro uses for Time Machine, and manually copy files to and from it (in other words, the correct SnowLeopard configuration does allow manual copying).
I have tried repairing the sparsebundle using the Disk Utility, which restores the ability to manually copy files to it, but Time Machine once again renders it unwriteable when it attempts to back up.
Anyone know of anything else I can try? Thank you so much!
Dan

Yeah, sorry about the broken link. I noticed that link wasn't working after I replied, then I edited my earlier reply. Also, yes, copying the files was just meant as a test; I created new clean sparsebundles for other tries.
Anyway, I'm not too worried about the resizing for now; first things first, let's just get Time Machine working with a sparsebundle at all.
I don't know how to make Time Machine create its own sparsebundle on my local drive; if there isn't a manually created sparsebundle at the root, it just puts everything in the "Backups.backupsdb" directory structure without a sparsebundle. However, it of course does create its own sparsebundle when I point it to my NAS share (as I understand it, Time Machine knows the NAS filesystem doesn't support everything it needs, so it creates the sparsebundle to emulate the correct filesystem). As I have always gotten the same "error -1" when using the NAS share as I did when using the local sparsebundle, I was assuming the same problem was happening in both cases... but now I've checked the console log after doing a backup attempt on the NAS share, and I see different stuff:
1/2/13 9:21:12.000 PM kernel[0]: AFP_VFS afpfs_mount: /Volumes/TM Backups, pid 9615
1/2/13 9:21:12.000 PM kernel[0]: AFP_VFS afpfs_mount : succeeded on volume 0xffffff8148d5b008 /Volumes/TM Backups (error = 0, retval = 0)
1/2/13 9:21:13.000 PM kernel[0]: AFP_VFS afpfs_unmount: /Volumes/TM Backups, flags 0, pid 9624
1/2/13 9:21:13.000 PM kernel[0]: AFP_VFS afpfs_unmount : We are the last mnt/sbmnt using volume /Volumes/TM Backups 0xffffff8148d5b008
1/2/13 9:21:13.000 PM kernel[0]: AFP_VFS afpfs_unmount : We are the last volume using socket /Volumes/TM Backups 0xffffff8148d5b008
1/2/13 9:21:49.647 PM com.apple.backupd[9623]: Starting manual backup
1/2/13 9:21:49.737 PM com.apple.backupd[9623]: Attempting to mount network destination URL: afp://[email protected]/TM%20Backups
1/2/13 9:22:00.060 PM com.apple.backupd[9623]: Mounted network destination at mount point: /Volumes/TM Backups using URL: afp://[email protected]/TM%20Backups
1/2/13 9:22:00.000 PM kernel[0]: AFP_VFS afpfs_mount: /Volumes/TM Backups, pid 9630
1/2/13 9:22:00.000 PM kernel[0]: AFP_VFS afpfs_mount : succeeded on volume 0xffffff8148ffb008 /Volumes/TM Backups (error = 0, retval = 0)
1/2/13 9:22:15.323 PM com.apple.backupd[9623]: Creating disk image /Volumes/TM Backups/iMac.sparsebundle
1/2/13 9:22:46.397 PM com.apple.backupd[9623]: Failed to hide extension on /Volumes/TM Backups/iMac.sparsebundle, error: Error Domain=NSCocoaErrorDomain Code=4 "The file “iMac.sparsebundle” doesn’t exist." UserInfo=0x7fe881407700 {NSURL=file://localhost/Volumes/TM%20Backups/iMac.sparsebundle/, NSFilePath=/Volumes/TM Backups/iMac.sparsebundle, NSUnderlyingError=0x7fe8814073c0 "The operation couldn’t be completed. No such file or directory"}.
1/2/13 9:23:10.209 PM com.apple.backupd[9623]: Failed to eject volume /Volumes/TM Backups (FSVolumeRefNum: -153; status: -47; dissenting pid: 0)
1/2/13 9:23:10.210 PM com.apple.backupd[9623]: Waiting 60 seconds and trying again.
1/2/13 9:24:10.241 PM com.apple.backupd[9623]: Network destination already mounted at: /Volumes/TM Backups
1/2/13 9:24:56.305 PM com.apple.backupd[9623]: Failed to eject volume /Volumes/TM Backups (FSVolumeRefNum: -153; status: -47; dissenting pid: 0)
1/2/13 9:24:56.305 PM com.apple.backupd[9623]: Waiting 60 seconds and trying again.
1/2/13 9:25:56.326 PM com.apple.backupd[9623]: Network destination already mounted at: /Volumes/TM Backups
1/2/13 9:26:40.171 PM com.apple.backupd[9623]: Failed to eject volume /Volumes/TM Backups (FSVolumeRefNum: -153; status: -47; dissenting pid: 0)
1/2/13 9:26:40.171 PM com.apple.backupd[9623]: Giving up after 3 retries.
1/2/13 9:26:50.177 PM com.apple.backupd[9623]: Backup failed with error: 21
1/2/13 9:26:50.178 PM com.apple.backupd[9623]: [SnapshotUtilities mountPointForVolumeRef] FSGetVolumeInfo returned: -35
1/2/13 9:26:50.178 PM com.apple.backupd[9623]: Failed to eject volume (null) (FSVolumeRefNum: 0; status: -35; dissenting pid: -1)
1/2/13 9:26:50.178 PM com.apple.backupd[9623]: Failed to eject Time Machine disk image: /Volumes/TM Backups/iMac.sparsebundle
So... looking through this, it does some mounting, which all works fine, then it does a create sparsebundle, which appears to work fine, but then it tries to "hide extension", but it can't because it can't find the sparsebundle that it supposedly created. Then it tries three times to eject the NAS share ('TM Backups'), and fails, and gives up. At this time I get the "error -1" pop up on my monitor, and check the NAS share (using the disk utility on the NAS managment page), and sure enough there is the sparsebundle "iMac.sparsebundle". So why does it create it, but then not be able to use it?
Skiing tomorrow, must sleep now. :-)

FileVault size not compacting

I've searched these forums for help with my situation and tried the hdituil suggestions but, so far, nothing has worked.
I'll give you the short version: I copied our music and photo libraries to our laptop internal drive so we could have them with us. Originally, I copied them to my user account but eventually realized that other users could not access it. Since I had only 40GB left on the internal HD, I had to use an external drive to complete the operation. I created an encrypted sparse bundle disk image on an external drive and copied the libraries to it. Then, I deleted the libraries from my section, logged out and back in to reclaim the space. I got most of the space back but not the entire 300GB (which was the size of the libraries). At the time, I thought nothing of it.
So I did some digging. According to What Size (UI for Unix command du), the two FileVault-ed account (disk image) files take up 127GB and 1.07GB respectively. Selecting all the files in each home folder, the disk image taking up 127GB is actually using 100GB. The account whose disk image is taking up 1.07GB is actually using 571MB.
Then, to be sneaky, I logged into the root account to attempt to compact them. When I did this, via Terminal, I got the following results:
For my disk image, it said: Reclaimed 3.8 MB out of 366.1 GB possible.
For my wife's disk image, it said: Reclaimed 0 bytes out of 464.2 GB possible.
Ok. So I found a post a week ago that gave instructions on how to reclaim the "missing" space. It mentioned needing Drive Genius 3 to accomplish this. Now that I actually want to read it, I can't find it.
Can anyone help? An idea what this means? Why doesn't the compacting that goes on when you log out of your account not reclaim all that space? It seems I could have an extra 28GB of space.
Thoughts or experiences? Thanks!

Welcome to Apple Discussions,
Apple's implementation of the FileVault sparsebundle's image apparently results in this peculiar observation - See this thread:
http://discussions.apple.com/thread.jspa?threadID=2227841
The apparent volume size of a mounted sparsebundle image is a "potential" size, which can be much larger than the current HD space occupied by the sparsebundle (hence the "sparse" in the name). Apparently the potential volume capacity of the mounted image can even be set larger than the HD itself, though it could obviously never be filled to that capacity by files because the sparsebundle could not grow large enough to hold them. What is also unusual in FileVault is that apparently a large fraction of the image capacity gets marked as "used" even before any files have been added to it, as described in the link above.
I guess the bottom line is that when you GetInfo directly on a FileVault Home (which is the mounted image), the "capacity" will be a number twice the size of the HD, the "available" number is probably accurate, and the "used" number is not meaningful because it reflects more than just the contained files.
If do want to see the size of the contained files, you could open a Finder window into the FileVault Home (showing the Documents, Music, Pictures folders, etc), and then type Command-A followed by Command-option-I. You will get an "Inspector" window which should show the total space used by the files, excluding the Trash.

Password fails in encrypted disk image

I created a 300 mb encrypted disk image using 10.4.x, about 9 months ago, now I am running 10.5.2 and everytime I try to open the image and type in the password (the correct password I have been using for years) iI get an authentification error. I know Im using the correct password, any ideas what happened here. Could the image be corupted but still want me to authenticate?
I have not tried to open the file since Dec. 17th (via last modified date) I have check all the permissions on the eternal drive where the file is stored... also ran Techtool on the drive and found no errors... I am out of ideas...

I have encountered the same problem on two protected disk image files as well. Once in January and then again a few days ago.
I first thought that the first lockout was a fluke. Now after the second image lockout I'm very vary of opening another encrypted backup. I'm losing data. Even copies of the .dmg on different drives fail to authenticate. Searching for answers I found this thread.
Is it possible that a kernel panic / forced shutdown can corrupt an encrypted file? I wonder, but my encrypted home directory (FileVault sparsebundle) is fine.
Any insights would be appreciated.
This is my log:
Last login: Sun May 11 07:35:13 on ttys000
kevin:~ kevin$ hdiutil attach -debug /Volumes/kevin/busted.dmg calling DIHLDiskImageAttach with
agent: hdiutil
drive-options:
debug: true
image-options:
verbose: false
quiet: false
main-url: /Volumes/kevin/busted.dmg
2008-05-12 18:11:17.015 hdiutil[1745:1c03] using helper tool at "/System/Library/PrivateFrameworks/DiskImages.framework/Resources/diskimages-he lper".
2008-05-12 18:11:17.040 hdiutil[1745:1c03] connectToFramework
2008-05-12 18:11:17.141 hdiutil[1745:1c03] sendOperationToHelper: about to ask proxy to start operation
status proc called: initialize
2008-05-12 18:11:17.173 diskimages-helper[1747:1603] _imageOptions: {
"enable-keychain" = 1;
2008-05-12 18:11:17.176 diskimages-helper[1747:1603] _driveOptions: {
autodiskmount = 1;
"unmount-timeout" = 0;
2008-05-12 18:11:17.178 diskimages-helper[1747:1603] DIHelperAttach: initializing framework
DILoadDriver: checking for disk image driver...DILoadDriver: DI_kextExists() returned 0x00000000 (0)...DIIsInitialized: returning NO2008-05-12 18:11:17.188 diskimages-helper[1747:1603] -checkForPreviouslyAttachedImage: entry
2008-05-12 18:11:17.189 diskimages-helper[1747:1603]
file://localhost/Volumes/kevin/busted.dmg - (null) ((null), (null)). perm=0
DIIsInitialized: returning YESDIBackingStoreNewWithCFURL: entry with
file://localhost/Volumes/kevin/busted.dmg
skip-permissions-check: true
DIBackingStoreInstantiatorProbe: entry
file://localhost/Volumes/kevin/busted.dmg
skip-permissions-check: true
DIBackingStoreInstantiatorProbe: probing interface 0 CBSDBackingStore
CBSDBackingStore::newProbe score 100 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 1 CBundleBackingStore
CBundleBackingStore::newProbe score -1000 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 2 CRAMBackingStore
CRAMBackingStore::probe: scheme "file": not ram: or ramdisk: scheme.
CRAMBackingStore::probe: score -1000 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 3 CCarbonBackingStore
CCarbonBackingStore::newProbe: setting initial rval to +100
CCarbonBackingStore::newProbe: has resource fork, +100
CCarbonBackingStore::newProbe score 200 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 4 CDevBackingStore
CDevBackingStore::newProbe: not /dev/disk or /dev/rdisk (/Volumes/kevin/busted.dmg).CDevBackingStore::newProbe score -1000 for
DIBackingStoreInstantiatorProbe: probing interface 5 CCURLBackingStore
CCURLBackingStore::probe: scheme is
file
CCURLBackingStore::probe: not recognized URL scheme.
CCURLBackingStore::probe: score -1000 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 6 CVectoredBackingStore
CVectoredBackingStore::newProbe not "vectored" scheme.
CVectoredBackingStore::newProbe score -1000 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreNewWithCFURL: CCarbonBackingStore
DIBackingStoreNewWithCFURL: instantiator returned 0
DIBackingStoreNewWithCFURL: returning 0x00000000
2008-05-12 18:11:17.190 diskimages-helper[1747:1603] -checkForPreviouslyAttachedImage: resolving file://localhost/Volumes/kevin/busted.dmg returned 0
2008-05-12 18:11:17.191 diskimages-helper[1747:1603] -checkForPreviouslyAttachedImage: imageUID (
"d234881039:i8914"
) shadowUID (null)
*** testing:
0: d234881039:i9111
(null)
(null)
*** testing:
0: d234881039:i9111
(null)
(null)
*** testing:
0: d234881039:i9111
(null)
(null)
2008-05-12 18:11:17.194 diskimages-helper[1747:1603] DIHelperAttach: resolving disk image
DIIsInitialized: returning YESDIIsInitialized: returning YESDIBackingStoreNewWithCFURL: entry with
file://localhost/Volumes/kevin/busted.dmg
enable-keychain: true
image-path: /Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: entry
file://localhost/Volumes/kevin/busted.dmg
enable-keychain: true
image-path: /Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 0 CBSDBackingStore
CBSDBackingStore::newProbe score 100 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 1 CBundleBackingStore
CBundleBackingStore::newProbe score -1000 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 2 CRAMBackingStore
CRAMBackingStore::probe: scheme "file": not ram: or ramdisk: scheme.
CRAMBackingStore::probe: score -1000 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 3 CCarbonBackingStore
CCarbonBackingStore::newProbe: setting initial rval to +100
CCarbonBackingStore::newProbe: has resource fork, +100
CCarbonBackingStore::newProbe score 200 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 4 CDevBackingStore
CDevBackingStore::newProbe: not /dev/disk or /dev/rdisk (/Volumes/kevin/busted.dmg).CDevBackingStore::newProbe score -1000 for
DIBackingStoreInstantiatorProbe: probing interface 5 CCURLBackingStore
CCURLBackingStore::probe: scheme is
file
CCURLBackingStore::probe: not recognized URL scheme.
CCURLBackingStore::probe: score -1000 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreInstantiatorProbe: probing interface 6 CVectoredBackingStore
CVectoredBackingStore::newProbe not "vectored" scheme.
CVectoredBackingStore::newProbe score -1000 for file://localhost/Volumes/kevin/busted.dmg
DIBackingStoreNewWithCFURL: CCarbonBackingStore
opening /Volumes/kevin/busted.dmg setPermission 1723
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
closing /Volumes/kevin/busted.dmg setPermission 1731
DIBackingStoreNewWithCFURL: instantiator returned 0
DIBackingStoreNewWithCFURL: returning 0x00000000
DIResolveURLToBackingStore: processing level 1 encodings.
DIFileEncodingNewWithBackingStore: entry for encoding level 1
DIFileEncodingInstantiatorProbe: entry for level 1
enable-keychain: true
image-path: /Volumes/kevin/busted.dmg
DIFileEncodingInstantiatorProbe: probing level 1 interface 0 CMacBinaryEncoding
CBSDBackingStore::openDataFork: about to open /Volumes/kevin/busted.dmg
opening /Volumes/kevin/busted.dmg openDataFork 1904
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
closing 3 /Volumes/kevin/busted.dmg closeDataFork 1984
00000000: 656e 6372 6364 7361 0000 0002 0000 0010 | encrcdsa........ |
00000010: 0000 0005 8000 0001 0000 0100 0000 005b | ...............[ |
00000020: 0000 00a0 548a 2877 86c1 4f17 877b cf66 | ....T.(w..O..{.f |
00000030: beea 6066 0000 1000 0000 0002 780e 1734 | ..`f........x..4 |
00000040: 0000 0000 0001 e000 0000 0001 0000 0001 | ................ |
00000050: 0000 0000 0000 0060 0000 0000 0000 0268 | .......`.......h |
00000060: 0000 0067 0000 0000 0000 03e8 0000 0014 | ...g............ |
00000070: d369 cd83 75e8 bb7c 72e5 020d fdd3 68a9 | .i..u..|r.....h. |
diskimages-helper: fileNameLength $0000006E
diskimages-helper: resourceForkLength $60000000
diskimages-helper: dataForkLength $00000000
diskimages-helper: commentLength $00006700
diskimages-helper: MacBinary III signature (0x00000000)
diskimages-helper: header CRC $0000FDD3
diskimages-helper: minimum decoder version $0000000D
diskimages-helper: encoder version $00000002
no MacBinary III signature - checking for MacBinary I or IIDIFileEncodingInstantiatorProbe: probing level 1 interface 1 CAppleSingleEncoding
CBSDBackingStore::openDataFork: about to open /Volumes/kevin/busted.dmg
opening /Volumes/kevin/busted.dmg openDataFork 1904
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
00000000: 7263 6e65 6173 6463 0000 0002 0000 0010 | rcneasdc........ |
00000010: 0000 0005 8000 0001 0000 0100 0000 005b | ...............[ |
00000020: 0000 00a0 548a .... .... .... .... .... | ....T........... |
closing 3 /Volumes/kevin/busted.dmg closeDataFork 1984
CAppleSingleEncoding::isAppleSingleFile loadAppleSingleHeader failed with error 22
DIFileEncodingInstantiatorProbe: probing level 1 interface 2 CEncryptedEncoding
CBSDBackingStore::openDataFork: about to open /Volumes/kevin/busted.dmg
opening /Volumes/kevin/busted.dmg openDataFork 1904
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
CEncryptedEncoding::copyHeaderInformation: inBackingStore->openDataFork returned 0
CEncryptedEncoding::copyHeaderInformation: inBackingStore->getDataForkLength (stub header) returned 0
CEncryptedEncoding::copyHeaderInformation: backingStore data fork length is 0x0000000278100000 (10604249088)
CEncryptedEncoding::copyHeaderInformation: reading V1 header from offset 0x00000002780FFB04 (10604247812)
CEncryptedEncoding::copyHeaderInformation: inBackingStore->readDataFork (stub header) returned 0
CEncryptedEncoding::copyHeaderInformation: not recognized as v1 header
CEncryptedEncoding::copyHeaderInformation: reading V2 header from offset 0x0000000000000000 (0)
CEncryptedEncoding::copyHeaderInformation: inBackingStore->readDataFork (stub header) returned 0
CEncryptedEncoding::copyHeaderInformation: reading auth-entry count from offset 0x0000000000000048 (72)
CEncryptedEncoding::copyHeaderInformation: inBackingStore->readDataFork (auth entry count) returned 0
CEncryptedEncoding::copyHeaderInformation: reading auth table from offset 0x0000000000000048 (72)
CEncryptedEncoding::copyHeaderInformation: inBackingStore->readDataFork (auth entry count) returned 0
closing 3 /Volumes/kevin/busted.dmg closeDataFork 1984
max-key-count: 1
blocksize: 4096
uuid: 548A2877-86C1-4F17-877B-CF66BEEA6066
version: 2
passphrase-count: 1
private-key-count: 0
CBSDBackingStore::openDataFork: about to open /Volumes/kevin/busted.dmg
opening /Volumes/kevin/busted.dmg openDataFork 1904
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
closing 3 /Volumes/kevin/busted.dmg closeDataFork 1984
CBSDBackingStore::openDataFork: about to open /Volumes/kevin/busted.dmg
opening /Volumes/kevin/busted.dmg openDataFork 1904
CBSDBackingStore::OpenLockFriendly: mapping flags 0x00000002 -> 0x00000026 (locks are MANDATORY)
(RW lock acquired)
closing 3 /Volumes/kevin/busted.dmg closeDataFork 1984
diskimages-helper: DiskImages secure mode enabled
CEncryptedEncoding:unclockCANTHROW: trying to unlock with normal keychain
UNLOCK: cannot find passphrase in keychain search list.
UNLOCK: SessionGetInfo returned 0
UNLOCK: sessionHasGraphicAccess
UNLOCK: sessionHasTTY
UNLOCK: sessionWasInitialized
UNLOCK: using TTY to prompt for passphrase
Enter password to access "busted.dmg":
unlockCoreFromTTY: passphrase is wrong
DIFileEncodingNewWithBackingStore: returning 0x00000050
DIResolveURLToBackingStore: level 1 encoding match failed. 80.
DIResolveURLToDiskImage: resolving backing store/file encoding failed. 80.
status proc called: attach
error code: 80
status proc called: cleanup
2008-05-12 18:11:41.081 diskimages-helper[1747:1603] DIHelperAttach performOperation: returning 80
2008-05-12 18:11:41.082 diskimages-helper[1747:1603] -decrementBackgroundThreadCount: _backgroundThreadCount is now 0.
2008-05-12 18:11:41.082 diskimages-helper[1747:10b] DIHelper reportresults: reporting {
payload = {
"result-code" = 80;
2008-05-12 18:11:41.083 hdiutil[1745:1c03] reportResultsToFramework: proxy has finished operation
2008-05-12 18:11:41.084 hdiutil[1745:1c03] reportResultsToFramework: results are: {
payload = {
"result-code" = 80;
2008-05-12 18:11:41.084 hdiutil[1745:1c03] reportResultsToFramework: _threadResultsError is 80
2008-05-12 18:11:41.085 hdiutil[1745:1c03] reportResultsToFramework: disconnecting from helper.
2008-05-12 18:11:41.186 hdiutil[1745:1c03] disconnectFromHelper: removing observers
2008-05-12 18:11:41.187 hdiutil[1745:1c03] disconnectFromHelper: terminating proxy
2008-05-12 18:11:41.189 diskimages-helper[1747:10b] DIHelper: terminateHelper: entry.
2008-05-12 18:11:41.190 hdiutil[1745:1c03] disconnectFromHelper: terminated proxy
2008-05-12 18:11:41.290 diskimages-helper[1747:10b] -DIHelperAgentMaster terminateUIAgentConnection.
DIHLDiskImageAttach() returned 80
2008-05-12 18:11:41.293 diskimages-helper[1747:10b] DIHelper dealloc.
2008-05-12 18:11:41.294 diskimages-helper[1747:10b] -DIHelperAgentMaster terminateUIAgentConnection.
hdiutil: attach failed - Authentication error
kevin:~ kevin$

FileVault1 TimeMachine and Lion

For a long time I didn't care about my TimeMachine setup because it "just worked", at least the last time I looked. Now I am unable to find old data in my time machine backup.
I am using FileVault to protect my home directory (I do not want do go to Full disk encryption if it can be avoided). Some time ago (at least with Leopard and Snow Leopard, cannot remember if with Lion, too) TIme Machine would back up my Filevault sparsebundle when logging out - it does not do this anymore. Also deleted Data in the Filevault sparsebundle doest not get freed after a reboot anymore, aparrently.
If FileVault 1 defunct in OS X Lion? Do I really need to go to FileVault 2 to have working backups anymore? Or is there some secret switch to reactivate backup of FV1? After all, the only data relevant to me is in the filevault container - I do not care about encrypting or backing up the OS and Applications.

schmadde wrote:
I am using FileVault to protect my home directory (I do not want do go to Full disk encryption if it can be avoided).
Why not? It's a vast improvement (I can't imagine why Apple kept the name).
Some time ago (at least with Leopard and Snow Leopard, cannot remember if with Lion, too) TIme Machine would back up my Filevault sparsebundle when logging out - it does not do this anymore.
Do you get any messages? Sounds like there's a problem, like damage to the encrypted sparse bundle.
Also deleted Data in the Filevault sparsebundle doest not get freed after a reboot anymore, aparrently.
Another reason to suspect corruption.
If FileVault 1 defunct in OS X Lion?
It was "iffy" on Leopard and Snow Leopard. Same in Lion. It was highly recommended to decrypt before upgrading to Lion, then use File Vault 2.
Do I really need to go to FileVault 2 to have working backups anymore?
It's much better. Backups work normally, just as with a normal installation -- all changes are backed-up hourly, and you can see and restore selected items from your home folder. As I understand it, once the whole drive is encrypted (long process, of course), there's very little performance degradation.
Or is there some secret switch to reactivate backup of FV1?
If the disk image is corrupted, and can be fixed, maybe.
After all, the only data relevant to me is in the filevault container - I do not care about encrypting or backing up the OS and Applications.
Yes, you do. If something awful happens (or has already happened), you're in a major pickle: a very tedious process to recover your stuff. In many cases, however, the sparse bundle can't be repaired, so is lost forever. Also see the pink box in Time Machine - Frequently Asked Question #11.
Via the Finder, open your internal HD, and drill down to the Users folder and locate the sparsebundle for the encrypted user account, something like this:
Leave that on the screen and start Disk Utility (in Applications/Utilities).
Drag the sparsebundle to Disk Utility's sidebar. That may take a few moments. Click First Aid in the toolbar, then Repair Disk. If no messages appear in the center of DU's window, select Window > Show log from the menubar.
Good luck, and keep us posted on the results.

Every time I shut down my computer, I lose all my settings - like things I removed from the dock are all back, the trackpad resets to original settings, etc. How can I get my preferences to stay like they used to? Thx!!

I recently went through a nightmare with my computer where there was an "old" operating system put on my computer and I guess File Vault was turned on. Since then I've upgraded and am now running 10.8.3 but got locked out of my old admin account when I tried to restore my computer from Time Capsule. Attempts to recover anything from my old admin account have been futile
So, I started a new Admin acct and have been trying to reconstruct my life, but every time I shut down and restart my computer, it erases/resets all my prefernces, like all the things in the Dock that I remove all come back and the track pad is always moving in the wrong direction again and has to be reset every time. Is there a way I make my prefernces stick??
BTW if anyone knows how to recover all my lost stuff that would be beyond amazing too
Thanks in advance!

Eustace, thank you so much for writing back. I will try what you suggested!!
thx for your reply - apparently when I went to the Apple store a long time ago, they restore maybe photos and itunes etc from my external hard drive (passport). I guess at that time they reinstalled an earlier operating system than my macbook came with and that somehow corrupted FileVault. apparently there was no sparse bundle (whatever that is) for my old admin account and they said that ever since the install of the older OS that it was actually NEVER backing up anything in my admin account.
Then, I bought Time Capsule and starting backing up to that instead. I started having problems with it being slow etc and then StartUp Disk full errors and didn't know what to do, so I "Restored" from Time Capsule and that's when I lost everything in my Admin account and was locked out when I tried to log in - it said File Vault error ..."
anyway - that's THAT sad story. I was told to create a new admin account and I've basically been trying to start over - even though I have a partial save of my computer in Crash Plan and I DO see a sparse bundle listed in there, but I just don't know enough about computers to know if it's something I can get back or if I am just totally doomed.
I'm afraid to reinstall anything because if there is even a remote shot that the other files are still floating around in my computer, I feel like that chance will be shot forever. I need to hire McGee from NCIS, I just KNOW he could get those files back for me!!!

The new firefox twitter app is great - except it disappears every time I shut down the computer and I have to remove and then reinstall it every day!?? I am working on an iMac - if that is causing the problem ...? Thanks.

The new firefox twitter app (mini tab on left of page) is great - except it disappears every time I shut down the computer and I have to remove and then reinstall it every day!?? It won't appear on the page until I do. I am working on an iMac - if that is causing the problem ...? Thanks.

Eustace, thank you so much for writing back. I will try what you suggested!!
thx for your reply - apparently when I went to the Apple store a long time ago, they restore maybe photos and itunes etc from my external hard drive (passport). I guess at that time they reinstalled an earlier operating system than my macbook came with and that somehow corrupted FileVault. apparently there was no sparse bundle (whatever that is) for my old admin account and they said that ever since the install of the older OS that it was actually NEVER backing up anything in my admin account.
Then, I bought Time Capsule and starting backing up to that instead. I started having problems with it being slow etc and then StartUp Disk full errors and didn't know what to do, so I "Restored" from Time Capsule and that's when I lost everything in my Admin account and was locked out when I tried to log in - it said File Vault error ..."
anyway - that's THAT sad story. I was told to create a new admin account and I've basically been trying to start over - even though I have a partial save of my computer in Crash Plan and I DO see a sparse bundle listed in there, but I just don't know enough about computers to know if it's something I can get back or if I am just totally doomed.
I'm afraid to reinstall anything because if there is even a remote shot that the other files are still floating around in my computer, I feel like that chance will be shot forever. I need to hire McGee from NCIS, I just KNOW he could get those files back for me!!!

Corrupt FileVault Sparsebundle

Similar Messages

Maybe you are looking for