How to recover partition (with encrypted sparse bundle disk image) that won't mount?

I have a Late 2013 27" iMac running OS X 10.9.4. I have an external drive that I use for Time Machine backups which also has an encrypted sparse bundle disk image. Yesterday, the drive stopped showing up in Finder, so I went to Disk Utility and tried to mount it. No go. So I tried repairing it, and it said it couldn't. I'm not worried about the Time Machine backup since my iMac is find so I can just make a backup to a new external drive. However, the encrypted sparse bundle disk image has some files in it that I don't have elsewhere. Is there a way to recover these files without sending it in to a drive recovery service (since those would cost a LOT of money)?

No such options. As I mentioned in the post title and in my first post, the partition won't mount.

Similar Messages

How do I change the password of an encrypted Sparse Bundle disk image?

I tried to change the password of an encrypted 'Sparse Bundle' disk image but it seems Disk Util doesn't let me choose this type of disk image for the Change Password function (Menu Imgaes->Change Password...)
How am I supposed to change the password? Do I really have to create a new disk image with a new password and copy the old one? (I'm using the 256 bits encryption)

There is no error. Just nothing happens. The problem is a little different for the sparse image and the sparse bundle image. When using the menu command Images->Change Password... you get a file dialog where you must point to the image. The sparse image is selectable (not grayed) but when selected nothing else happens. The sparse bundle image is grayed out in the file dialog so you can't even select it.
Something else. When creating a new blank disk image it shows up in the left pane of the Disk Utility app. But after unmounting the images I'm left with Disk1, Disk2 in this list. Re-mounting doesn't change that. It seems rather useless as you can't do anything with them.
All this happens consistently on multiple Mac's, all with 10.5.2

Does Time Machine still ignore mounted disk images? Specifically, encrypted sparse bundle disk images?

My Time Machine backs up to Time Capsule which cannot be encrypted. I also have confidential data in an encrypted sparse bundle disk image in my home folder. When TM backs up and the encrypted sparse bundle disk image is mounted and I'm accessing the data, does TM back up the data "in the clear" decrypted form or does it exclude the disk image because it's mounted? I've done a little research, but there's conflicting information. Not sure what happens in Lion now...

Time Machine does not backup mounted disk images! The encrypted sparse bundle disk image was mounted, I updated a doc and did a TM backup - the file was not listed in the TM repository and the doc remained unchanged in the encrypted sparse bundle disk image on TM. Then I ejected the disk image and did a TM backup - the updated doc was backed up in the encrypted sparse bundle disk image! Thank you!

Can't share sparse bundle disk image

I'm trying to create a sparse bundle disk image in /Users/Shared for sharing between two users on the same computer. No matter what I've tried, the disk always mounts as read only for the non-owner user. I've tried creating the disk image in both accounts, adding the non-owner user with "read & write" permissions, changing all permissions (including everyone) to "read & write," but nothing seems to help. Does anyone have any experience sharing sparse bundle disk images using the shared folder?
Christopher

I realized after reading the replies above (thank you, A.Carlo and KJK555) that I was only applying permissions to the top level of the sparse bundle image and not to the underlying directories and files in the package. This was what was keeping the second user from making changes to the mounted disk image. After digging a little deeper into possible solutions, following is what I decided to do.
First, here are the requirements for my sparse bundle disk image:
1. Full permissions (rwx) for user1 and user2
2. No permissions (---) for everyone else
3. Directories and files created by user1 or user2 need to be fully accessible (rwx) by the other user
In order to block access to the sparse bundle from unwanted users and to allow for inherited permissions for all future directories and files, I took the following steps:
1. Created a new group (group1) with user1 and user2 as members
2. Created a new folder (Example) under /Users/Shared
3. Removed all permissions from the new folder for everyone but user1 (chmod 700 Example)
4. Added an ACL to prevent group everyone from deleting the new folder (chmod +a "group:everyone deny delete" Example)
5 Added an ACL to give group1 full permissions (rwx) to the new folder and allow those permissions to be inherited by new directories and files created within that folder (chmod +a "group:christophertemple allow list,addfile,search,add_subdirectory,delete_child,readattr,writeattr,readextattr,writeex tattr,readsecurity,file_inherit,directoryinherit)
This is what the new folder looks like from Terminal:
$ ls -le
total 0
drwx------+ 4 user1 wheel 136 Sep 18 12:45 Example
0: group:everyone deny delete
1: group:group1 allow list,addfile,search,add_subdirectory,delete_child,readattr,writeattr,readextattr,writeex tattr,readsecurity,file_inherit,directoryinherit
This folder is now accessible only by user1 and user2 and any files or directories created in this folder will be accessible by both users, regardless of which of the two users created them.
Next, I created an encrypted sparse bundle disk image within the new folder. In Terminal, the disk image looks like this:
$ ls -le
total 0
drwxr-xr-x@ 6 user1 wheel 204 Sep 18 13:03 Example.sparsebundle
0: group:group1 inherited allow list,addfile,search,add_subdirectory,delete_child,readattr,writeattr,readextattr,writeex tattr,readsecurity,file_inherit,directoryinherit
As can be seen above, the new sparse bundle has inherited the group permissions from the parent directory, giving user1 and user2 full access to the disk image.
While I could have added a few extra steps and changed the permissions of the mounted disk image, I decided against doing so; the default permissions were perfect for my use. By default, the mounted disk image is set to "Ignore ownership on this volume."
When mounted by user1 this is how the disk image looks in Terminal:
$ ls -le
total 8
drwx------ 7 user1 staff 306 Sep 18 13:01 Example Disk Image
When mounted by user2 this is how the disk image looks in Terminal:
$ ls -le
total 8
drwx------ 7 user2 staff 306 Sep 18 13:01 Example Disk Image
With these permissions, no user, other than the user that mounted the image, has access to the image while the image is mounted. This is useful from a security standpoint, keeping others from viewing the contents of the disk image, as well as from a data integrity standpoint, allowing only one person to access files on the disk image at a time (important for some of the data base files the image contains).
Thanks again to those that responded. I hope this post is helpful to others who might have similar requirements as I did.
Christopher

Time Machine and mounted sparse bundle disk image - file by file backup?

I think I had this system working in Leopard, but upon upgrade to Snow Leopard it seems to have broken. Does anyone have any idea how I can get Time Machine to back up the contents of a mounted sparse bundle disk image in real time - file by file within the disk image? For example, I have a 2GB sparse bundle disk image that i keep all of my bank statements/files/records in. It auto-mounts on boot and stays mounted. I use the disk image to keep it password-protected, so if I unmount it it is fairly safe. In Leopard, I would exclude the .sparseimage file from backup, but it would still backup the mounted image itself on a file-by-file basis, so I could enter Time Machine and explore the image folder by folder, file by file (say I deleted an old bank statement by mistake, I could go into time machine and recover as if it were a normal file/folder).
In Snow Leopard, after a clean install, and creating a new sparse bundle disk image and excluding the .sparsebundle file, I can't seem to get this to work even though the image is mounted. Is there any way to trick Time Machine into backing up the mounted image as it would any other folder? I know I can back up the .sparsebundle file incrementally but in order to recover a lost document I'd have to remount the old bundle and that seems rather roundabout.
Thanks,

I think you're trying to bypass the finder to mount the disk. Try this (I'll bold the key steps):
- *Turn off Time Machine* in the System Preferences.
- Option A: If you directly use a hard disk (not wireless) that has the sparsebundle you want to open, *connect the disk* but don't double click on the sparsebundle.
- Option B: If you are using wireless, this means use shift-command-k (or shift-apple-k), and if it says "Connect As..." in the upper right instead of disconnect, then use that button to *connect to that wireless drive*.
- Confirm the sparsebundle shows in that folder before proceeding...
- *Open Terminal* (Applications>Utilities>Terminal.app)
- Type: *hdiutil attach -noverify* (<-- notice a *space " "* must be included after typing this here but *DON'T hit return* yet.)
- *Drag the sparsebundle to the cursor in terminal*, and it should fill in something like /Volumes/HardDrive/COMPUTERNAME.sparsebundle for you. Now you can hit return, and the disk will mount.
- After you are done browsing sparsebundle's mounted image, *eject the mounted disk* like you would any other disk (not the sparsebundle image itself, just the disk icon that appeared if you successfully mounted it).
- Turn *Time Machine back on* in the System Preferences.
Hope this helps.

Can I put Network Users on a sparse bundle disk image?

Hello! Can anyone out there help me figure out what seems to be a rather complicated feat? I'm trying to get users to log in to client iMacs as if they were local accounts, but the user account information is stored on a sparse bundle disk image.
Long story short, I've currently got OS X Server running network user accounts tied to Active Directory. When the users log in, they have a sparse bundle disk image that automatically mounts on their desktop. This has been an effective solution for some of our software that doesn't play well with Network storage, as the sparse bundle is treated like local storage by the Macs.
However, what would be a much better solution for us is to actually have the whole user account stored on the disk image. It's a little like the way FileVault 1 worked, except the disk image is actually stored on a network drive. So far, as a proof-of-concept, I've been able to make this work manually: I've had to log in to a local admin user and then mount the user's sparse bundle with all their user folder contents contained within. Then, once the user path is changed to point to the disk image, the user logs right in, everything works exactly as expected (once I got the permissions set correctly). This method works exactly like a Network User account except that all the applications see it as local storage instead of network storage.
The trick, though, is automating this process. I want a user to sit down in front of any iMac, log in and go straight to their account. It would be nice if OS X Server was able to accommodate this with a setting, but it doesn't. So, my plan so far has been to create a generic local account with a script on the desktop that users can open to login in. The script would then mount the network share, then mount the sparse bundle disk image, then log the user in to their "local" account on the iMac. When they log out, there's a login hook that restarts the machine.
So far, I'm stumbling over the fact that the sparse bundle unmount when logging out of the generic "login" account, preventing the user from logging in. But if I leave the generic account logged in, then the loginhook to restart the computer doesn't work.
Any feedback or suggestions would be greatly appreciated!

IIRC, sparse images only grow as things are added, but do not shrink. Create a new one, mount the original, transfer your stuff from the original into the new one, and delete the original one.

Problem with sparse & sparse bundle disk images

Lion (OS 10.7) is driving me carzy.
Setting up sparse and sparse bundle disk images goes fine. But sometimes when attempting to open the image later, particularily after adding content (JPGs) I get the spinning beachball and then I must restart the computer. I have restarted this computer more than all my others put together, going back to OSA 7.
Other times everything seems to work fine
I have a G-5 running OS10.5, and there is no problem. The system is very stable re disk images.
I've tried all kinds of work-arounds with limited success. These include changing the names of the disk images or the files in them. Usually, I'm back to restarting the computer. If I copy an image that doesn't work on the Mac Pro to the G-5, it'll work. Sometimes the number for the size of the image in list view is grayed out and I don't know what that means.
It's interesting that when I first got the Pac Pro with Lion installed, sparse and sparse bundle images wouldn't work at all. After several updates to 10.7.2 or 3, the disk images work, but are not stable.
I would be very grateful if anyone out there has any info or hopefully an answer for this situation.
Thank you - kajz

More from kajz
Sorry about the typos in my first message. I was tired after fighting the sparse image problem with Lion.
Today I have tried read/write disk images (dmg) and so far they seem to work fine. I would prefer sparse or sparse bundle disk images since they only take as much room as their contents, but I'll have to be practical about this.
The frustrating thing is that sometimes the sparse or sparse bundle images seem to work, but just when I relax, I'll open one and see all the blank square icons for each of the jpg files, and then I know I'll have to restart the computer.
I'm still hoping that someone else has had this problem and that maybe there's an answer. Maybe it'll take a future update by Apple to fix this.
Thanks in advance - kajz

Can't get free space after deleting a file-sparse bundle disk image

I have a 150 GB Sparse bundle Disk image with a 256 AES enc. I just deleted about 30 GB worth of tv shows to free up some space but the Disk Image is still the same size with no more free space on the virtual disk either. I know that with Filevault the user has to log out in order to recover free disk space but how does this work with a normal Sparse disk image? Thanks in advance!
-Macguy3000

IIRC, sparse images only grow as things are added, but do not shrink. Create a new one, mount the original, transfer your stuff from the original into the new one, and delete the original one.

Sparse bundle disk images

I've been doing a lot of reading about (and watching tutorials about) sparse disk images and sparse bundle disk images.
Most of what I've read has addressed using sparse disk images as a way to archive and move from Mac to Mac FCPX projects and their associated events. But I have a some questions:
1) Isn't it better to always use a sparse bundle disk image rather than a sparse disk image? I use Carbon Copy Cloner, and it seems like for backup programs that periodically do incremental back ups of changed files, the sparse bundle disk image is a better choice. But is there any downside to using a bundle image? Is it somehow slower?
2) Why not create and edit every project and its event(s) from the start on its own sparse bundle disk image? I know that isn't a good idea with at least some networks, but I don't have a network. The advantage that I can see is that if you make make duplicates of projects to preserve certain versions as backups, and the associated events are all on the same sparse bundle disk image as the project, you can use Finder to move the image around and all of the references between the projects and events will remain the same no matter how many times you move the project.
3) Are there any downsides to using disk images from the start? For instance, would they somehow slow down the editing process?
Thanks

ken |ken|noun [ in sing. ]one's range of knowledge or sight: such determination is beyond my ken .

Sparse Bundle Disk Image

Hello,
I've come accross a little issue that I cannot seem to find the solution for.
I don't use TimeMachine but do use FileVault which I have enabled on my account.
Now, my account is stored in the main partition of my harddrive which has roughly 100GB and it is now full! However, I know I don't have that much stuff stored on the laptop and started investigating where all that space was gone.
It seems that my /Users/.paul sparse bundle disk image is around 80GB large!!
However, if I du -kh on my /Users/paul folder, I only get 23GB...
Several questions that someone might know the answer to:
1) Why is there such a big difference
2) how can I administer what's inside of the Sparse bundle disk image?
3) How can I delete stuff from inside it that I don't see anyway in my user folder...
Kind regards,
Paul

Hi and Welcome to  Discussions!
Sparse images automatically adjust their size when needed, but they do not decrease in size automatically when you delete stuff inside. But you can compact the image to the space acutally needed via Terminal. To do so you need to use hdiutil as explained here: http://www.macosxhints.com/article.php?story=20040625012304236
Have fun!
Björn

Use Sparse Bundle Disk Image for sharing library among users?

Apple's knowledge base article HT1198 (http://support.apple.com/kb/HT1198) on sharing iphoto libraries among multiple users on the same Macintosh describes using a sparse disk image in the /users/Shared/ directory. For a Mac that uses a Time Capsule for Time Machine backups won't this require the entire iPhoto library to be backed up anytime a picture is added or modified?
Would using a sparse bundle disk image instead work better?
Also, HT1198 doesn't say anything about "Partitions" parameter setting in Disk Utility when creating a blank sparse image or sparse bundle disk image. Does it matter what setting is selected if the image is being kept on the Mac internal disk drive?
Is there any difference between iPhoto '08 or iPhoto '09 when attempting sharing the iPhoto library among users?

I believe it may require the entire bundle to be backed up. You'd best ask that question in the Time Machine forum. They would know more about the ins and outs of TM there.
If you can afford an external FW hard drive that would be the best option by far. No worry about filling up the sparse bundle, and you could use the external HD as a work platform to help keep a minimum of 20 GB of free space on your boot drive for optimal performance of system and applications.

How to recover partition with osx after install

yea so i decided to install win 7 using bootcamp and made a partition for 50gigs. after following instructions the win 7 install menu came up were the partitions are located, and on the bottom it showed the partition i made for 50gigs that read (bootcamp partition) or something similar, anyways i clicked on it and it told me that win 7 could not be installed on that partition. so i clicked on advanced and then clicked on "format" again to reformat the partition again. after win 7 was installed succesfully and a few reboots later i cannot access or even see osx anymore. i know what and why its not showing up i just dont know how to reinstall the bootloader to access the partition again. does any dual boot loader work ok or what is the best way to make this work. thank you for any help in advanced.

When starting the system hold down the Option/Alt key to get a boot selection screen. Select Mac OS X to boot from. If by chance there is no OS X boot selection then you formatted the wrong partition and wiped out OS X. If that is the case you'll need to start over reinstalling OS X or restore from your Time Machine backup.

How do I mount a disk image that won't open?

I have an external drive Samsung 500 GB that was failing. I think my MacBook Air (10.6.8) caused it to fail because it wouldn't allow me to eject the disk even though I forced quit all programs. I eventually had to just unplug the drive and this caused the external disk to fail as it had not been ejected properly. Not my fault. It's the MBA's fault for not letting me eject the disk. Now the Samsung disk won't mount properly and I get a message that the drive is failing and I should save the data.
Anyhow, I used the free version of Data Rescue 3 to try and save the data on the failing Samsung 500 GB drive and move it onto a brand new Toshiba 1 TB drive.
I was unable to use the normal scanning function of Data Rescue 3 as the hardware of the drive was too damaged, and so I used the clone function on Data Rescue 3 to clone the data onto a non-failing hard drive, with the intent of restoring the data later.
I am not sure if I was successful in making the disk image. It hung up at the 99.6% point for about 12 hours when I decided to give up on it, and I shut down Data Rescue so I could eject the hard disks.
However, it would not let me do it. I tried force ejecting but still I could not eject the disks.
I ended up just unplugging the drives. I think the Samsung drive died almost completely then because it made a whole lot of clicking noises after that (it was only making a few clicking noises before that).
Anyhow, I plugged the Toshiba 1 TB drive into the computer again and used Data Rescue to scan the drive with the disk image on it to see if I could detect files on that drive.
It opened up the structure and I was able to see that most or all of the files were there (abbout 450GB of data) just from seeing the information about the files in the structure tree - the labels of the files (file type labels such as jpg, mp4 etc) and the size of the files, although I could not open up the files to check all of them.
I tested out the restore function of Data Rescue by downloading one file (<10MB) file. I am using the free version and can download one file for free to test things out.
It worked and I was able to save that file onto a second external drive (Western Digital 500 GB) I had plugged in. I had bought this drive just to do the data rescue.
So I think the files are salvageable and the disk image is OK.
However, when I tried to open the disk image in Disk Utility, by opening it as the source and choosing the WD drive as the destination I could not open it. I got an error message. I can't remember what the message was.
I tried just opening the disk image in Finder by just clicking on the disk image but it won't mount.
Is that because my hard drive doesn't have enough space? My Desktop on the MBA only has 12 GB free and the WD drive has only 500 GB on it even though the disk image is about 501 GB.
I don't know why the disk image is that size when the failing Samsung drive only had 450 GB of data on it.
Anyway, what should I do to mount the disk image?
I want to mount the disk image so that I can copy or move the files from it to another external drive so that I can save those files.
Is it because the WD is only 500 GB or does it mean there's a problem with the disk image I made?
Should I try Carbon Clone Copy? I use that to make backups of my MBA internal HDD though I have never used it for opening or making disk images.
I have never dealt with disk images before except for dmg files of applications downloaded from the internet.
I am trying to avoid using Data Rescue 3 as I have to pay for it and if there is a free option, such as Disk Utility, CCC or other, I want to try it to restore the data in the disk image.
Sadly, I think the Samsung drive is ruined beyong repair as it's making a lot of clicking sounds and doesn't mount properly in Disk Image and I get a message that it's beyond repair or something like that in Disk Utility.
So I am relying on the disk image I made on the Toshiba drive to restore my files.
(I think it was the last movie file that caused the problem because it was when I was trying to copy it onto the Samsung external drive, all the problems began - hanging up when copying it, not being able to eject the Samsung disk, causing hardware issues on Samsung disk and getting warning messages on Disk Utility.)
BTW, I learned how to eject a drive when it won't eject the normal way, I have to use command window and type in commands, but that's another post ....
Any advice?
I am thinking of going out and buying a second 1 TB external drive so that I have a disk with enough space to open the 501GB disk image on it, just in case that was the sole problem.
However, I am not sure that is the case, and I think there may be a problem with the disk image or I am not going the right way about opening it.
Thanks for any advice.

I think I've found the solution to this problem.
http://superuser.com/questions/19426/im-unable-to-mount-a-dmg-getting-a-no-mount able-filesystems-error
I am following the instructions here:
I ran into a similar situation. I did what simonair suggested and I received a message in Terminal that Volume mounted successfully. However It did not help me access the mounted Volume neither was I able to confirm the mounted Volume. Nor was I able to mount the image using Disk Drill or even scan through. Nothing succeeded.
Here is what I did to solve my problem. I see that in this post some suggested that we should convert name.dmg to writable file. I used the command from Terminal to convert but was not successful. INSTEAD alternatively, I used Disk Utility, attached the Volume (yes I got the same message again, ''no mountable system files'' however, Disk Utility nevertheless attached the image, which I was able to do before anyways. This time, I selected it and then clicked New image, and then selected image format read/write, not the compressed option. I created a new image. This time this image was writable however, it still would not mount using Simonair's solution. However, this time I was able to scan it with Disk Drill with exact file locations and folder hierarchy as I had. Recovering all from thereon was a breeze. Just remember: when you create new image of an attached volume and chose not compressed but read/write, you need to have a disk with exact amount of space that totals the total space allocated within that name.dmg file (not the amount of space the data takes). Mine was huge, and luckily I had an external disk with enough space to do that and it took about 5 hours for about 400GB of disk allocation. Good luck.
And so far it seems to be working. Even though the volume is grayed out on the left side of Disk Utility, I am still able to select it as the source for making a new disk image. I chose Read and Write and no compression.
The only thing I might be doing differently is that instead of choosing the disk image as the source, I chose the volume as the source. The volume is grayed out, but the disk image is not.
It seems to be working all right. Keep my fingers crossed.
If this doesn't work, I will use Data Recovery 3 as a last resort.

I want to encrypt data using disk image - will the encryption be retained when the data is backed up by Time Machine?

I want to use the Disk Image utility to create secure, encrypted information storage on my Mac. I am using Time Capsule with Time Machine to back up my hard drive. Will the file still be encrypted on Time Capsule? I am concerned that if someone had access to Time Capsule they could get the data that I want to protect.

If you're not already, you should consider using a sparse bundle disk image as it is more compatible with Time Machine.
With a regular disk image, the image is a single file. If you make changes to the internal files, the entire image will have to be backed up. With a sparse bundle, the image is split into lots of small files. That way, only the small part that contained the changes will need to be backed up.
If the image is small, it doesn't matter much, but if the image is 50GB, you don't want to waste 50GB Of backup space for a 5KB change.

How to deal with apparent sparse bundle corruption?

I set up Time Machine over the weekend - backing up my MacBook Pro to my Power Mac G5. It seemed to be working fine yesterday morning. When I came home from work the TM icon reported that it had failed and the sparse bundle no longer appeared as a mounted disk. I can connect to the main disk just fine but the sparse bundle seems corrupt.
I tried using Disk Utility (on my G5 - figured that would be faster) to repair the sparse bundle. That failed miserably, completing immediately, reporting no errors, but telling me the disk image was only 204 bytes. (du reports that it is 69GB.) There is still plenty of free disk space on the parent drive (129GB free).
I'm running 10.5.8 on both machines. What now? Is the sparse bundle toast?
Thanks,
Skip Montanaro

unfortunately, that's one of the main problems with Time machine - it's not sufficiently reliable for a backup application. there are all kinds of bugs and then you can have issues like your when the sparse bundle with backups can become corrupt. that's why it's a good idea to have a secondary backup using a different backup solution. many people (myself included) use CCCloner or Superduper to create bootable backups in addition to using TM.

How to recover partition (with encrypted sparse bundle disk image) that won't mount?

Similar Messages

Maybe you are looking for