Using Encrypted Disk Images

When I create an encrypted sparse bundle disk image it starts small an grows when I add files. When I create a sparse disk image it starts at the size I set and never grows. I understand all this however, what I don't understand is gaining FREE space again. When I delete a file I don't get back the free space on the mounted virtual drive but the disk image is still the same size! I know that filevault (which basically just places your home folder in an encrypted Sparse bundle image) some how recovers space, is this possible with other ENCRYPTED disk images as well?
Thanks in advance,
Macguy3000

A sparse image file can expand but it does not automatically contract as data is removed. I believe I remember reading a hint at MacOSXHints.com about how to resize a sparse image file.

Similar Messages

  • Encrypted disk image on external drive prevents that drive from ejecting

    I've tested this a few different ways, and it seems to be a rather consistent problem.
    I have an external USB hard drive (seagate) and on that drive I use encrypted disk images to store my data.
    (because it's a portable drive, I'm nervous I'll lose it and then someone will have access to my stuff).
    So anyway, whenever I mount the sparse bundle disk image, when it comes time to eject the drive (after ejecting the disk image of course), it hangs for a while and then the Finder says it can't eject, but that I can Force Eject the drive.  When I chose to Force Eject, it works, but I don't like having to force it every time.
    Anyone know what's up?
    Thanks,
    Brian.,

    Open Disk Utility > File > New >Blank Disk Image...
    or use the "Option-⌘-N" Key combo (with Disk Utlity open).
    Kj

  • Corrupted files within encrypted disk images

    Greetings Apple Hivemind:
    I've run across a repeatable problem when using encrypted disk images from Disk Utility.  Essentially, I'll create an image using settings like are shown below:
    The disk image is then used for storing data.  In my case, this is usually data for Adobe Lightroom.
    At first, this worked very well, and I housed the disk images on my household NAS, connecting via samba (smb) to it on my Mac.  Over time, however, something odd started happening:  Files on those encrypted images began getting corrupted whenever I tried writing new data to them.
    My first incident was where Lightroom informed me that the catalog it was trying to open was corrupted.  I  tried to create a new one on the same encrypted volume, and it too was instantly flagged as corrupted.  I opened the individual image files on the volume with no problem, so I wasn't thinking that the volume was the culprit.  That is, until I tried dragging new image files to it manually.  The new files were immediately either completely unreadable, or a mish-mash of the content of random OTHER files on the volume!
    The result was that all old data seemed intact, but I could no longer write new data to the volumes without major data corruption issues.  I thought that this was isolated to one volume in particular, but it soon started happening on ALL of my encrypted volumes eventually.  Including those which were not, and never had been, housed on my NAS, but were on my local hard drives.
    I've since "evacuated" all my data from these images, since the ones created by Disk Utility appear to be useless, and am seeking an alternative.
    Is this something that anyone else has encountered when using encrypted disk images?  It seems like this is something I should really open a support ticket for, but I can't say I've ever tried it, so I don't know how successful it would be to do so.

    bbonn wrote:
    I should add that I've tried using the "Repair" and "Verify" functions of Disk Utility on the volumes, and despite the obvious issues that exist in them, the utility doesn't find (or fix) any inconsistencies.
    Are you repairing/verifying the actual disk images, or just the partition they're on?  If the partition, it won't look inside them.
    Drag one to Disk Utility's sidebar, select it, then use Verify or Repair.  Note: the usual messages may not appear on the DU window.  Click the Log icon in the toolbar or select Window > Show Log from the menubar to see them.

  • Even though I have LCD font smoothing disabled, Mountain Lion still uses it in PDF views, Safari's location bar, Mail's message view, and the dialogs for mounting encrypted disk images.

    Even though I have LCD font smoothing disabled, Mountain Lion still uses it in PDF views, Safari’s location bar, Mail’s message view, and the dialogs for mounting encrypted disk images. Is there any solution to this problem? Also diabled the Smoothing in the SystemPrefs and also via Terminal. Font smoothing is still there. Very annoying, especially in PDF attachments in Apple Mail.

    Try feeding Safari a user-defined CSS file with font-smoothing tweaks (including none). The filename and its filesystem location are arbitrary. Use your favorite coding editor.
    Safari > Preferences > Advanced > Style Sheet:
    Here is an example with all elements uncommented. Pick the one that works best for your Safari viewing and comment out the others:
    Preview. Try Preview > Preferences > PDF > Smooth text and line art (uncheck)

  • Unable to unlock encrypted disk images created with Snow Leopard using Lion

    Anyone else unable to unlock encrypted disk images created with Leopard and Snow Leopard with Lion?  I know that they made changes with the release of FileVault 2 on Lion and Snow Leopard cannot use Lion encrypted disks but I thought it was backwards compatible where Lion should still be able to work with Snow Leopard created images (it was in the pre-release versions of Lion).
    When attempting to mount an encrypted disk image created with Snow Leopard on Lion the normal password prompt appears but then just reappears every time the password is entered and does not unlock and mount the image.  I'm positive the correct password is being entered and it works just fine when done on a machine running Snow Leopard.

    Not in cases when the computer successfully boots to one OS but produces three beeps when an attempt is made to boot it to another. If it really was a RAM problem that serious, the computer wouldn't get as far as checking the OS version, and it has no problems booting Lion. In the event of a minor RAM problem, it wouldn't produce three beeps like that at all.
    (67955)

  • Unable to create an encrypted disk image in Lion

    disk utility gives the error Unable to create "Volume.dmg." (error - 60008) when creating an encrypted disk image. I am using the following steps:
        1.    Open disk utility
        2.    Select the disk (internal or external) to create the image on
        3.    Select File>New>Blank Disk Image…
        4.    Save As: 'Volume'
        5.    Name: Volume
        6.    Size: 50GB
        7.    Format: Mac OS Extended (Journaled)
        8.    Encryption: 128-bit AES encryption
        9.    Image Format: read/write disk image
        10.    Click the Create button
        11.    Password dialog appears
        12.    When I enter a password the dialog closes after entering only a few characters i.e. before I've finished typing, and the following error message displays:
    Unable to create "Volume.dmg." (error - 60008)
    I have previously, successfully, created encrypted disk images in Snow Leopard, and I don't know why I can't in Lion
    Does anyone have any ideas?

    Thanks for this Thomas.
    I've tried naming the image differently, but still received the error, I did however try different permutations for the password.
    The error seems to happen if I use a purely numerical password string and occurs on input of the 10th numerical character, if I start with numerical character but use an alpha before the 9th number I can continue and create a password, and I can create a password  if I start with an alpha and switch to numerals after the first alpha character, purely alphabetical passwords are fine too.
    It seems that Lion doesn't like purely numerical passwords greater than 9 characters, whereas Snow Leopard wasn't so fussy. Seems it's a bit of a bug.
    Thanks for your help

  • Unable to create an encrypted disk image with Disk Utility

    Hi:
    With our upgrade to Lion a few weeks ago, we're now unable to create an encrypted disk image of any type using Disk Utility any more. This problem occurs on 3 different machines, and is reproducible whether one is using an internal HD or an external FW HD. We can successfully create nonencrypted disk images.
    This is a duplicate post with all the details here: https://discussions.apple.com/message/18469359#18469359
    We haven't had any luck with a solution trying various permissions fixes as helpfully suggested by other readers in response to the error message # (-60008 error), so I'm hoping that someone else has run across a solution from the encrypted disk image perspective and that this tag line will generate some help.
    Thank you!

    Save As: 01 (on Desktop)
    Name: 01
    Size: 100 MB
    Format: Mac OS Encrypted (Journaled)
    Encryption: 256-bit AES
    Partitions: Single partition- Apple Partition Map
    Image Format: read/write disk image
    At the password window that pops up I enter: 1234567890
    This says password strength is "Weak"
    All works fine
    Then I repeated this using:
    Save As: 02 (on Desktop)
    Name: 02
    Size: 100 MB
    Format: Mac OS Encypted (Journaled)
    Encryption: 256-bit AES
    Partitions: Single partition- Apple Partition Map
    Image Format: read/write disk image
    At the password window that pops up I enter: 1234567890 and when I start to enter the next "1" I get the "Unable to create "02.dmg." (error -60008)
    OS 10.7.4
    Disk Utility Version 12.1.1 (353)

  • Disk Utility - Create encrypted disk images super sloooow

    Trying to create encrypted disk images via Disk Utility on my iMac (i7 8GB) is super-slow in 10.8.   It worked quite fast in 10.7, but now it's super-slow and doesn't even seem to ever finish.
    I've tried re-installing 10.8 with no difference.
    Anyone else having trouble with this?  Even a small dmg (~200MB) doesn't seem to work.
    Unencrypted images seem to work OK (if not a little slow).
    I realize that the encryption process will be slower but something is definately wrong with 10.8 disk utility in this regard.  I have 1TB+ free space.  I have tried with another user account as well.
    My task was: (new disk image, read-write, 128bit encryption)
    2012-09-03 08:59:59 -0400: Initializing…
    2012-09-03 09:00:00 -0400: Creating…
    2012-09-03 09:03:28 -0400: Copying…  <<< seems to be stuck here...

    Good morning,
    Have you tried using Disk Utility from within the recovery mode? (Hold down CMD and R when booting)
    I used to have this problem but creating them this way really improved the time.
    Give it a go...
    Rob

  • Indexing of encrypted disk images permanently disabled in 10.8?

    In the past, I've had no trouble forcing Spotlight to index my encrypted disk image, using the command in Terminal:
    sudo mdutil -i on /Volumes/Encrypted_Data
    After entering that command, my encrypted disk image was indexed and searchable using Spotlight.
    A couple weeks ago I updated from Lion to Mountain Lion. Today I noticed Spotlight wasn't showing any results from my encrypted disk image. So went back to Terminal and entered the above command. Instead of successfully activating indexing, Terminal gives me this message:
    /Volumes/Encrypted_Data:
                Indexing disabled.
    Is this procedure now impossible in Mountain Lion?
    Is there any way to enable indexing of this encrypted disk image? I can't get it to work.
    Thanks.

    I appear to have solved the problem to get Spotlight to index a disk image.  My image was an encrypted disk image.  I was able to get spotlight to work when it was new, but now Spotlight won't index it.  Here is the solution that I found:
    After double clicking and mounting disk the image, open Disk Utility, select the disk image file, then click unmount in the Toolbar.  Wait until it is unmounted, then click mount again.   Then go to terminal and try mdutil -sa .  If it is still not enabled, try to sudo mdutil -i on option.  The unmounting and remounting must be done everytime the image is opened.

  • HT1578 Labels (Mavericks) not working in encrypted disk image?

    I created an encrypted disk image with Disk Utility.
    I placed a file in the opened encrypted disk image, and labeled it with "test".
    If I open a finder window and look for files labelled "test" the file doesn't appear.
    This message is placed under the wrong OS, because it is not possible to choose Mevericks from the popup list!!!!

    Where I used the word label I did mean tag

  • Encrypted Disk Image creation slow?

    I just got a new MBP with Leopard. I have created a number of encrypted disk images in the past using Tiger and a MBP and have not had any trouble. This weekend I tried a few times to create a 50 gig encrypted disk image (128 AES) on an external drive and after going through the process of setting it up and waiting for it to be created, (and watching the progress bar as it was being created), after about 45 minutes NO progress was showing on the progress bar. I ended up having to cancel the creation a few times because I thought something was going wrong. I’m not sure if there is a problem creating the disk image, or leopard is slow, or what.
    Does anyone know how long, on average, it would take to create an encrypted disk image of this size using leopard? I just want to know if there is a problem doing this on my MBP. Thanks for the help.

    A regular 50 GB disk image takes 50GB of space, no matter if it is full of files or empty.
    A 50 GB sparse disk image only takes up the amount of space equivalent to that of its enclosed files. So if the 50GB sparse image only has 1 GB of files inside, the image won't be much bigger than 1GB.
    A sparse bundle is similar to a sparse image, but instead of a single file it is a folder package with many, many enclosed files called bands. A new file added to the sparse bundle will tend to modify only a few bands. This makes incremental backups of a sparse bundle more efficient because only the changed bands need to be backed up again. Any change to a sparse or regular disk image will mean that the entire image will need to be backed up again.
    If you regularly add/remove files to a disk image, and you intend to back up that disk image with Time Machine, a sparse bundle is definitely the way to go. The other types will fill up your TM volume very quickly.

  • Encrypted disk image creation very slow-

    I just got a new MBP with Leopard. I have created a number of encrypted disk images in the past using Tiger and a MBP and have not had any trouble. This weekend I tried a few times to create a 50 gig encrypted disk image (128 AES) on an external drive and after going through the process of setting it up and waiting for it to be created, (and watching the progress bar as it was being created), after about 45 minutes NO progress was showing on the progress bar. I ended up having to cancel the creation a few times because I thought something was going wrong. I’m not sure if there is a problem creating the disk image, or leopard is slow, or what.
    Does anyone know how long, on average, it would take to create an encrypted disk image of this size using leopard? I just want to know if there is a problem doing this on my MBP. Thanks for the help.

    A regular 50 GB disk image takes 50GB of space, no matter if it is full of files or empty.
    A 50 GB sparse disk image only takes up the amount of space equivalent to that of its enclosed files. So if the 50GB sparse image only has 1 GB of files inside, the image won't be much bigger than 1GB.
    A sparse bundle is similar to a sparse image, but instead of a single file it is a folder package with many, many enclosed files called bands. A new file added to the sparse bundle will tend to modify only a few bands. This makes incremental backups of a sparse bundle more efficient because only the changed bands need to be backed up again. Any change to a sparse or regular disk image will mean that the entire image will need to be backed up again.
    If you regularly add/remove files to a disk image, and you intend to back up that disk image with Time Machine, a sparse bundle is definitely the way to go. The other types will fill up your TM volume very quickly.

  • Encrypted disk image on a network, is the data encrypted during reading/writing?

    I'd like to use an encrypted image for storage of sensitive data on an openly accessible network storage. Does anyone know if the data that is written/read from the image (once it is mounted) is transferred over the network in an encrypted or decrypted form?
    It's seems important, since if the network connection is not encrypted then the data might be accessible to others.

    Efren,
    When you mount an encrypted disk image, the machine you are using (and on which the image is being mounted) is handling all encryption/decryption. So yes, the data that is transmitted across the network is already encrypted.
    Scott

  • Can a 256 bit encrypted disk image be read by Tiger?

    I have computers running Leopard, Tiger and Panther.
    If I create a 256 bit encrypted disk image in Leopard, will the image be able to mount and used for reading and writing in Tiger and or Panther?
    Or should I use 128 bit encryption in a mixed OS X environment?
    TIA,
    Bill

    Hello Bill,
    A 256 bit encrypted disk image created in Leopard can be opened in Panther, and presumably Tiger, though I don't have Tiger.
    It cannot however, be written to, only read.
    So if you want to add to the disk image on Panther, and possibly Tiger, use 128 bit. But if you only want *read only* on the other machines you could use 256 bit.

  • Encrypted disk image sometimes mounts without password

    I have an encrypted sparsebundle disk image containing sensitive information.  On occasion (maybe one time out of ten), I'm able to mount it without being prompted for the password.
    The password for the image is not stored in my keychain.  Can anyone offer advice on this issue?

    I was having exactly this same problem!
    I keep a small encrypted disk image storing sensitive banking information. I do NOT have the option to store passwords in Keychain checked, and I verified that the password is not being stored in Keychain.
    Yet, when I double-clicked the supposedly encrypted sparsebundle disk image, it opened right up and mounted - no password required! Unbelievable, right? So I started to investigate.
    I first noticed this behaviour in Mountain Lion, I'm running 10.8.4 on a 2.7 GHz 15" MBPr.
    In past versions of OS X I would mount the volume to work on it by double-clicking on the disk image, enter my passowrd, and then Eject the volume either by dragging to the trash or clicking the Eject button on the Sidebar. The next time I would try to access the disk image by double-clicking it, it would again prompt for a password. All good.
    What seems to be happening in ML is, using the same workflow, even though the volume is disappearing from Finder, the disk image is not actually being unmounted!
    When I go to Disk Utility, the disk image is still mounted, but the volume is grayed out. When I Eject the disk image in Disk Utility, it then reverts to the expected bahaviour, and double-clicking on the disk prompts for a password.
    So the workaround seems to be when finished working on the volume, go to Disk Utility and manually Eject the disk image (as opposed to just the volume it mounts) to ensure it has unmounted and is thus again encrypted. The reason for it sometimes requiring a password, sometimes not is probably because after a restart of the computer it would unmount all disks, and then be unable to re-mount it until the password is entered. But in between, unless you were aware of this behaviour anyone with access to the disk image can view its contents.
    What a terrible security flaw IMO, as there is no visual indication in Finder that the disk image is still unprotected after you unmount its volume and that icon disappears! I'm surprised this hasn't gotten more attention.
    Incidentally brian_c, I tried to look at your linked videos but it returns the message that the videos violated the TOS of the site...?

Maybe you are looking for