Removing an encrypted disk image

A while ago, I created a 7gb encrypted read/write disk image and put some files in it. Now, recently, I removed the files in the encrypted disk image and copied them back into the regular HD. I erased the mounted disk image and now says it's back to 7gb.
How do I remove the disk image? It's still there in my documents folder. How do I melt it back into the HD space? I can remove it from the side bar on the disk utility page but it's still on my HD and I can still mount it to the finder. I enter my password and it mounts.
I want to get rid of that disk partition as I don't use it anymore. What do I do? Is it there forever and am I stuck with it?
Thanks in advance for anybody that can help me with this.

Niel,
You know I actually tried that before but the trash was hanging and hanging. I have it set to empty securely and I know it takes longer for secure empty but it was really long.
I'll try it again but is that normal? Does the encryption have anything to do with it?
Thanks for the help, hope this time it works.

Similar Messages

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 mounts without Password

I've created a new encrypted disk image so that I can store sensitive documents and did it carefully, step by step,(per instructions from www.macworld.com/2425) but after I unmounted, then remount, it doesn't ask me for a password. It just mounts as if it were a regular file. Am I suppose to unmount the volume and drag the disk image to the trash? I don't know what else to try.

The Mac uses and encrypted database of keys called the "Keychain". When you login, it opens the "login" keychain using your login password. That keychain can be used to provide passwords for applications and services, and form data for web sites. In this particular case, the password for your encrypted disk image is being stored in the keychain and automatically provided.
If another user attempted to open the disk image, the disk image mounter would first look in his keychain and then the system keychain for a key to open it with. Finding none, it would prompt the user to specify the key (password). If the user supplies the correct password, the system would put it in his keychain for safe keeping, and the user would then be able to open the image again without supplying the password.
You can remove the key from your keychain by opening up /Applications/Utilities/Keychain Access, selecting the "login" keychain, and then looking for an entry with a name that matches the .dmg file in question. Highlight it, and then press the delete key to delete it. The next time you attempt to open it, it will prompt you for a password.

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$

Nested items in docked folder inaccessible on mounted encrypted disk image

When I click on a folder in the dock, then select a nested folder and try to open it, I get the error message:
"The application cannot be launched. -35"
The folders in question reside on an encrypted disk image (which is mounted). If I remove the folder from the dock and then put it in the dock again, this fixes the problem until the disk image is unmounted, and then mounted again.
Are there any solutions? Thanks.
iMac G5 10.5.7

I finally discovered a quick and easy workaround for this problem.
Using Automator and Cocktail's "built in" Automator actions, I created a script with 2 actions. The first clears the user's dock caches (using Cocktail). The second action is a shell script that relaunches the dock. The script is simply "/usr/bin/killall Dock" (case sensitive, without the quotes).
I saved the Automator script as an application and dragged the app into my Dock. Now, all I have to do is click on the app in the dock, and click allow in the window that pops up (allowing the app to obtain the password for Cocktail from my keychain) and then the nested items then become immediately available. I don't have to reset any prefs regarding the appearance or behavior of the docked folders. Problem solved!

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.

Encrypted disk image access privileges

Hi,
I use an encrypted disk image to store my important documents.
It remains mounted most of the time because I keep accessing or modifying files there (but at least, I know they're not accessible to anyone stealing my machine, plus if feel more secure uploading the whole image disk for backup purposes and in some contexts, I am careful to unmount the disk image).
It is stored on a Mac that I occasionally share with other people.
I have noticed that when these other people log into their account, they have access to the content of the mounted image disk.
Does anyone know a way to prevent that access? I have already tried removing all access privileges to any users, both on the disk image file and on the mounted volume but that did not change anything at all (only I and the special user "staff" have any privileges to the file and the mounted volume).
Does anyone have any idea how I can get MacOS X to hide the volume to any other users than me?
Thanks!

Where is it stored – in your home folder?
Select your_image.sparsebundle (may have a different file extension)
press command + i
set permissions
     me r+w, staff r (is fine), everyone no
mount the volume (doubleclick)
press command + i
set permissions
     me r+w, everyone else no
uncheck
     ignore ownership

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)

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

Create encrypted disk image with OS install disk utility.

I thought to make a full backup of Macintosh HD, and followed instructions in /kb/ht1553. However, every time I tried to creae an encrypted disk image, it barfed with "Failed - User interaction required". I assume it needed the encryption password, but for some reason was unable to display a prompt for this. Anyone know how to fix this? Thanks, Stephen.

Create an encrypted sparse disk image instead of from folder, mount it, and then drag & drop your files into ii.

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

Creating an Encrypted Disk Image on an External (USB) Drive

I have an external 600 GB drive (2x 300 GB SATA 3.5" disks in a Thecus N2050 RAID0 external enclosure connected to iMac by USB2) onto which I would like to backup a large amount of data (500 GB).
I store this external drive away from my home (in the office) and since I cannot guarantee physically locking away the drive I would like to logically lock the drive by placing all the backup data into an encrypted disk image created on that volume.
I have tried creating an encrypted disk image on my USB volume in Disk Utility (Apple's instructions here) but I experience a number of issues not documented in the Apple article:
1) I am not presented with a drop-down option for the size of the disk image.
2) When I go ahead and try to creat the image I am told that the creation was impossible "file or folder does not exist".
Is it possible to create disk images on USB volumes (I cannot create such a large disk image on my iMac HDD as I do not have sufficient space).
thanks in advance
Raf

I realised that in Disk Utility you must not have any of your mounted drives highlighted in the left hand pane.

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.

Removing an encrypted disk image

Similar Messages

Maybe you are looking for