Cannot see encrypted disk image in ML

I created an encrypted disk image (password protected folder) through Disk Utility in Snow Leopard. However, now that I have upgraded to Mountain Lion, that folder appears to have vanished or is invisible. All my other file are intact but I just cannot see this encrypted folder anymore.
Anyone else having the same experience or able to offer some pointers?
Thanks,
Peter

There would be no reason for Mountain Lion to hide it. That's not normal behavior. Mountain Lion follows the same rules in this regard that Snow Leopard did. But, you can certainly check to see if it has somehow become accidentally hidden by entering the following command into the Terminal (but don't press return yet):
ls -al
Make sure there's a space at the end, and then drag the folder in which the .dmg file used to reside onto the Terminal window. This will enter the path to that folder in the command. Now switch back to the Terminal and press return. Do you see the .dmg file in the listing? If so, copy and paste the Terminal output into a message here, and I can give you a command that will show that file again.
If it's not there, it must have been accidentally deleted. (Again, not normal behavior, so most likely either it was accidentally deleted by you or someone else who uses that machine or the hard drive is badly corrupt and files are going missing.) Do you have a backup of that file?

Similar Messages

DIsk Utility, encrypted disk image

I cannot create an encrypted disk image. I have searched through the discussion forums here but have not found an answer. After I select the name, location, image format, encryption and I hit save, I get an error that says "Unable to create '[file name].dmg'. (Resource busy)". I've tried different locations, image format and encryption, but I keep getting the same message. Any ideas what the problem is and how I can fix it? Thanks.
NB: I want to create the disk image so that I can encrypt a few files with sensitive information. I do not want to use filevault, as I understand that it has downsides (e.g., free space needed to turn on and off, and backup with TM).

1. Open the Disk Utility application. (If you don't know where it is, search for it in the spotlight.)
2. At the top of the Disk Utility window, you will see several icons. Click on the one labeled "New Image". Before you do this, make sure that none of the drives on the left column (including "Macintosh HD") are selected.
3. A new window opens. It asks you for the name you want to give the new disk, and where you want to save it to (you can choose to save it on the desktop). It will also ask you for the volume size of the new disk (the default setting is 100MB, but you can give it any size you want). It also asks you for the volume format, encryption (128- or 256-bit; 128 should be enough, unless you want to make it more secure, but compromise a bit of speed), partition (there is no need to partition; in fact, many recommend no partition at all), and image format (if you plan to frequently add and delete files on your encrypted disk, "sparse bundle disk image" is recommended".
4. Click "create". It will ask you to create a password for your disk image.
5. The new disk image should appear on your desktop (or other destination you chose). Double-click on the image to open it. It will ask you for your password. Enter the password you selected. You can choose to save the password on your keychain. That defeats the purpose of encrypting the disk image, since anyone who gains access to your computer will not have to enter the password to open the disk image and see its contents.
I hope this step-by-step guide helps you. Let me know if something is not clear or if I got something wrong.

Encrypted disk image mount error

When I try to open one particular encrypted disk image, a Warning dialog box opens with the following message:
The disk image you are opening may be
damaged and could damage your system.
Are you sure you want to open this disk image?
If I answer yes, the image mounts and I can see at least the one file I tried.
I don't want to risk ruining the contents of the disk image, so I am not using
it anymore, and have run Disk Utility/First Aid on it.
By running this script while Disk Utility "Repairs Disk":
{ while [ 1 ]; do ps axlwww >> psout; sleep 1; done; }
I can see that Disk Utility runs:
/sbin/fsck_hfs -y -f -g /dev/disk1s2
to check a mounted disk image. This works fine on a good encrypted disk image,
but Disk Utility shows these errors for the broken one:
A Warning dialog box opens with the following message:
First Aid failed
Disk Utility stopped repairing "Safe" because the
following error was encountered:
The underlying task reported failure on exit
and the first aid window shows:
Verify and Repair disk "Safe"
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Invalid sibling link
Volume check failed.
Error: The underlying task reported failure on exit
1 HFS volume checked
1 volume could not be repaired because of an error
Any ideas how to fix this? I tried running
/sbin/fsck_hfs -y -f -r /dev/disk1s2
from the terminal, but it complains:
** /dev/rdisk1s2
** Checking HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
** Cannot repair volume when it is mounted with write access.
** The volume Safe could not be repaired.
and running it on the parent .dmg file doesn't work at all.
Thanks,
Scott

Well, I wish you luck, but haven't seen many people fix busted images.

Writing to Encrypted Disk Image SLOW On Mac Pro

I have a slew of Previous Gen (2010/2012) Mac Pro 12-Core 2.66 desktops running 10.8.5 (12F45). When making a standard 128-bit Encrypted Disk Image, the write speed to that image is extremely slow. Disk image is on the same system internal drive as the source material. Also tried on Gigabit Ethernet share. 1GB file takes 20 minutes.
If I take the same disk image and run it on a 2012 Mac mini server 2.6 i7 running 10.8.5 (12F45), the write speed is fast; 1GB takes 1 minute. Same holds true for a MacBook Pro (non-Retina) 2.3 i7 running 10.8.5 (12F45).
Antivirus is disabled on all machines for testing purposes. Mac mini is actually a clone of the Mac Pro's system, so everything is the same, software-wise.
Is there something inherently wrong with these Xeon Mac Pros that they cannot write fast to encrypted disks? Any other variables I'm not thinking of?
Thanks in advance.

The write speed to an encrypted image is around 5.65MB/s in comparison to 92MB/s on normal disk. I feel frustrated to see the remaining time to copy 800GB of data from internal HDD to the mounted encrypted volume takes around 1 day. An encrypted disk managed by Truecrypt on any PC will work much better than it.
iMac (Late 2013), OS X Yosemite (10.10.1)

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.

Encrypted Disk Image Won't Partition After Resize

Hi,
I have a 10 GB encrypted disk image on my macbook (type OS Extended (journaled)). I've pretty much filled up the space so I want to resize. I go into disk utility with the disk unmounted and 'Resized' it to 20GB. Then I mount it and go into the Partition tab. I drag the corner all the way down to fill up the space and hit Apply. It goes through the motions without error but it does not actually extend the partition to the resize. On the right next it then says something to the effect that the disk is read only and cannot resize the partition. The write status is read/write until I click apple....then it switches to 'Unmounted, read-only'. Any ideas on how to fix this? It's driving me crazy. I can provide screenshots when I'm home from work if necessary.
Thanks
Nick

Here are some screenshots of before and after I try to partition (after the resize):
After attempting to resize the partition it says 'The disk is not writable and can't be partitioned' and 'The disk is too small to contain partitions'. The disk write status also changed to read only. Doesn't make sense to me...anyone know how to fix this?
Thanks

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 to Password Protect Folder Not Working!

I have followed the instructions exactly for creating a Disk Image in order to password protect a folder. Folder contains multiple types of files including images, pdfs, etc. Here is what I've done and what happens:
In Disk Utility I created a New Disk Image from Folder. I chose the folder, which I have on my Desktop, and clicked Image. I gave the Disk Image a new name, placed in on my Desktop, indicated the image format as read/write and chose the 128-bit encryption. I chose a very strong password and unchecked the remember password box. At this point, all seems to have gone well.
Now, back to my Desktop. I have two things going on.
1. The initial folder that I wanted password protected is still present. Am I supposed to just send this to the Trash?
2. When I double click on the the new .dmg file that I've created, I am asked for my password, which I put in. Then, nothing. I mean, nothing happens. It doesn't open, it doesn't do anything. I can click on it and choose Open with DickImageMounter, and nothing happens. I can open with Disk Utility, but this just gives me the normal options to eject, burn, restore, etc.
I don't know why I can't get this to work properly, and I'm a little annoyed that Apple can't make it as simple as selecting a folder and having the option to password protect it, just like you can a normal file. PLEASE HELP!
Thanks.

As of OS X 10.7.4, Disk Utility had a bug that prevented it from creating an encrypted disk image with a password of more than 10 characters. I haven't checked recently to see whether that bug has been fixed, but from your report it seems not to have been. There is a workaround, but it's complicated.

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!

Creating a LARGE Encrypted Disk Image

Hello,
I have to encrypt a LARGE external Hard Drive for my work (a 1 Terabyte external drive, which comes to about 930 gigs to encrypt).
I have to do one of the regular encrypted disk images, not one of those expandable ones.
I know that encrypted disk images take a long time to create, as I’ve created smaller ones in the past and they take hours.
Does anyone know how long it will take to create an encrypted disk image of this size?
AND, since it will probably take quite a while, I was wondering if it is BAD for my MacBook Pro or the external drive itself to write information for this long of a period. I just want to make sure I don’t damage anything.
Thanks for any help.

I did a 400 GB one and it must have taken an hour to get the password prompt, a couple more for the creation, and another for formatting and mounting.
If you have a bed and sleep daily, as I suspect you do, start an hour before bed, enter the password and it should be done by morning.
You don't need a 900 GB image unless you have one 900 GB file which I doubt. Make one smaller one say 300, then copy it twice. The password will be the same in all 3 copies.
If you look at activity monitor not much is going on during all this so don't think the house will burn down (or your pants - see other question posted today).

Can't paste password for new encrypted disk image.

Howdy all!
I have been trying to create an encrypted disk image with the Disk Utility, but I'm having trouble with putting in the password.
Using the password assistant, it only fills one of the two password fields, and I cannot copy/paste the password to the other field. If I generate a password elsewhere I cannot paste it into either box as well.
If I switch applications from Disk Utility and come back to the password dialog the menubar says I am still in whatever application I was last (in this case it says Firefox at the very left) and the Edit menu is completely grayed out.
Any idea how to get a non-typeable password into this dialog?
Thanks for your help.
Mike

You can paste it in if you use hdiutil to create or mount the disk image (In Terminal.app). That's the
only way to go if you use a "bullet proof monster" password like I do.
To create an encrypted, sparse disk image, open a Terminal window and cd to the directory in which
you want to create the image file. For example:
cd ~/Desktop
Then type the command:
hdiutil create -size thesize -encryption -type SPARSE -fs HFS+ thename
live command example:
hdiutil create -size 1g -encryption -type SPARSE -fs HFS+ myimage
(this will create a 1gigabyte sparse image with the hfs format with the name "myimage.sparseimage"
#note: I love sparseimages and sparsebundles because they mount so quickly#
Above, the size is the maximum size that the volume will ever be able to contain, for example,
660m for 660 megabytes or 1g for one gigabyte. Note that if you want the image file to remain
below a certain size (such as the size of a CD) you must allow for approximately 10% overhead.
Also above, thename is the name of the image file you want to create, not the volume name.
The volume name will be "untitled". Rename as you would any other mounted volume (after it is
mounted).
You will be asked for a password or phase to secure your file. In terminal you may copy and paste
or use command + V keyboard combo. It will mount normally after that.
I don't use the "Remember password (add to Keychain)" function because my passphrase will be
visible in the Keychain to anyone with physical access to your computer.
Instead I use Terminal to open my new image.
Open terminal.app, simply type:
hdiutil attach /path/to/imagefile
example:
hdiutil attach /Users/kj/Desktop/myimage.sparseimage
(remember, you can drag and drop the file path into the terminal from Finder)
Terminal will ask for your password, simply cut and paste from your favorite password program
(such as "1Password").
There is a manual page available; type man hdiutil in the Terminal.
Enjoy,
Kj

Encrypting Disk Images

Hi,
I've followed several guides to create an encrypted disk image so i can hide some private files on my Mac - All the guides said the same way and one was the one here on Apples site and still i have no luck.
I create the disk image and when i put the files in it, eject the disk and try to mount the disk again from the DMG file it doesn't ask for a password. The only solution i can see is that it is because this does not work as i am admin and trying to password a file in my on account? Does this only work for shared folders with other users or is there another explanation as to why this won't work?
Thanks

Well Keychain is really there for your convenience. It remembers your passwords so that you don't have to enter them when they are needed but it is sort of a security risk of you just leave your mac sitting there and your keychain unlocked. However, these passwords can only be used while the keychain is unlocked. An admin password is needed to actually view the password.
You can lock an unlock the keychain manually or have it lock automatically after a certain amount of time (in keychain access go to Edit -> Change settings for keychain "login") or when your mac sleeps. But you might want to consider the security of your mac as a whole instead of just the keychain. For example: is it easier to keep the keychain locked or is it easier to prevent access to your computer as a whole (like disabling automatic login and requiring a password from waking from sleep?).
Steve

Encrypted disk image partitions

I wish to create an encrypted disk image using Disk Utility. One of the menus, labeled Partitions, contains 8 choices, 5 of which begin with the words "Single Partition." The 3 that I think I need to consider are:
Apple Partition Map
Master Boot Record Partition Map
GUID Partition Map
I have no idea which to choose to simply store personal data files. Is there some place where all of this is explained, or can someone please explain it here.
Thanks, Ralph

Thanks to both responders. Assuming that I only wish to install data files, I don't care about booting an operating system from the disk image that I wish to create. Therefore, I assume that V.K.'s response answers my particular needs.
However, that brings up another question. If one chooses a GUID Partition Map to be able to boot in an INTEL Mac, does that mean one cannot boot from that partition with a PPC Mac? Also, the same question with an APM Partition Map. In other words, does one have to choose one or the other and there is no way to do both, that is, be able to boot from the same partition with either PPC or INTEL? Just wondering...

Cannot see encrypted disk image in ML

Similar Messages

Maybe you are looking for