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.

Similar Messages

  • Adding files to encrypted disk images

    Here's what I'd like to do:
    - Select a file or folder "foo" with Finder
    - Go to my AppleScript menu bar item and choose a script to do the following:
    1) Mount an encrypted disk image (I already have one made); the password is not in my keychain so I'll need to be prompted to enter it
    2) Copy "foo" to the top level of the mounted disk image
    3) Unmount the disk image
    4) Move the original file to the trash
    5) Secure empty the trash
    I don't speak AppleScript very well; can anyone help?

    Thanks, Niel. You are always so helpful.
    I couldn't get it to work, though. The disk image wouldn't mount with the "open file" command. So I changed the first line to:
    do shell script "hdiutil mount ~/Documents/Miscellaneous/files.sparsebundle"
    That works; it prompts me for the image password and then mounts the image. So far so good.
    But then it stops with this error message:
    Can’t make {} into type alias.
    Do you know how to fix it?

  • My Automator script to backup files to encrypted disk image

    Hi there. I have a question regarding Automator and Encrypted disk images. I've put together a workflow that grabs files in my home folder. My home folder is utilizing FileVault. I'm grabbing things like my iphoto library, documents folder and such. On an external usb drive I've created an encrypted disk image about 100GB. My goal is for the automator action to "successfully" mount > copy > unmount the encrypted image.
    As of right now, the script works, but gives an error at the end of the copy, not allowing a successful unmount of the dmg. Is there something I'm doing wrong? I browsed through all the files after copying and they are all there, the folder sizes match up 100%.
    I guess I could just use a program that does this, but, I find it much easier clicking on a shortcut in my dock to run the script and go away for 10 - 15 mins.
    If it would help to view the script, let me know and we'll work something out.
    Thanks

    The popup box says:
    The action "Copy Finder Items" encountered an error. Check the action's properties and try running the workflow again.
    And the Automator workflow log says:
    Can't read directory contents: /Volumes/Backup
    But as I said, clearly it works and reads/writes to the encrypted dmg because all the files are there. What I do is just select all the folders inside the drive first, and delete/empty the trash first before running the action. This is the second step once I know this is working. So that I don't have to manually delete them everytime before running the script.
    So to answer your question, the drive is empty, and the dmg is empty, allowable for a maximum 100GB of storage.
    I think it might be something to do with copying files to an encrypted disk image, but, I can't find any help anywhere on this.
    Thanks

  • Can't read any file within a disk image

    A year ago I created a disk image with a few thousand files in as an archive. Periodically I open it and access the files.
    Now when I open the dmg, I see all the folders and files, but none of them are usable. No application can open them, for example opening a jpg in Preview yields the message " The file “Picture 1.jpg” could not be opened. It may be damaged or use a file format that Preview doesn’t recognize. " I get similar meesages from Word, Acrobat, etc. for their files. Basically it appears that every file in the dmg is corrupt.
    I have run Disk Utility Repair which said no repair needed; I have run DiskWarrior which found and fixed problems; neither made a difference.
    Any suggestions? Running 10.6.8.
    Thanks

    Sorry that I'm late to this party, but in case somebody else comes by this thread, this is the way to measure the voltage from the 20V plugs:
    http://www.kawakami-ca.com/images/20v_dc_plug.jpg
    Ray Kawakami
    X22;X24;X31;X41;X41T;X60;X60s;X61s;X300;X301;Z60m;Z61t;Z61p;560Z;600E;600X;T21;T22;T23;T41;R50;A21p;A22p;A31 and A31p
    Not a Lenovo employee; just a volunteer helping out here
    All personal links to PC-Doctor software removed 8/2012 by mfg request

  • Alias to open a file in an encrypted disk image

    Deleted.

    There is a quick and simple test, could someone with Lion installed be so kind as to do this:
    1. Use Disk Utility (or Knox if they own the app) to create an encrypted disk image on the Desktop called Test
    2. Mount the image, open TextEdit and paste a page of text into the window, then save the file in the mounted disk image
    3. Paste another page of text into the TextEdit window
    Open Terminal, navigate to /Volumes/Test, view the hidden files in the directory & post the results here.
    All you need to do to clean up is eject the disk image then drag the .sparsebundle file to the Trash.
    Cheers

  • How does one save new files to an encrypted disk image?

    I encrypted a particular folder, and used a sparse image to leave plenty of room, as well as using read/write permissions, but I don't see how to save new files to the encrypted folder.

    So, I guess you have to save the file to the desktop and then drag it to the mounted disk?
    No, you should be able to save directly to a mounted disk image via a dialogue box. There is no need for an intermediate step. As long as the encrypted disk image is mounted, it is open and appears to be just another folder.
    As an experiment, open a Textedit document and save it to the mounted (open) disk image via Save As in Textedit. It should be able to do that.

  • File Vault on HOme Directory with encrypted disk image in it

    I want to try File Vault. My question is as follows: I have an encrypted disk image already in my home folder. It is a small 500 MB one. Can I keep that in there, as is, without problems, or is File Vault going to encrypt and encrypted image and cause some sort of problem?
    Has anyone done this without issues?
    I know the alternative is to unencrypt my current image and let File Vault handle the encryption, but I am curious about leaving it alone and trying File Vault.
    Thanks for any help,
    x-.-x

    x-.-x wrote:
    I want to try File Vault.
    Good luck!
    File Vault going to encrypt and encrypted image and cause some sort of problem?
    FileVault is no more likely to scramble an encrypted disk image than it is to scramble the rest of your files. However, it is quite likely that it will scramble all of your files.
    Has anyone done this without issues?
    I have read many postings here in the discussion forums by people who have used FileVault and lost all of their data. Your mileage may vary. The only way I would use FileVault would be if I had an unencrypted copy of everything somewhere safe. Like you, I keep a small encrypted disk image for particularly sensitive files.

  • 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?

  • 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$

  • Can't create encrypted disk image

    With Leopard, I have repeatedly followed the instructions for using Disk Utility to make an encrypted disk. All appears to go well...all fields appropriately filled, including 128 encryption. But when I hit create, either nothing happens, or I get a second Disk Utility starting window. In any case, I am not asked to create a password, and am unable to find any trace of the disk I thought I'd just created. Would welcome your thoughts.

    While creating, make sure that it's saved to the desktop so you will know where it is supposed to be, at least.. Was wondering if posssibly you lost them. Look for the named disks in your home folder and in HD on chance they are there somewhere.
    I know you went to Help but just making sure you are creating disks this way (below). Everything worked fine for me--
    If things still don't work, turn off DU and move to the desktop "com.apple.DiskUtility.plist" in your home folder/library/preferences. A new file will be created when disk utility is turned on again. Deleting plist files don't usually don't solve problems but sometimes they can become corrupted.
    Good luck
    RM
    1 choose File > New > Blank Disk Image.
    2 Type a name for the image, and choose where you want to save it.
    3 In the Volume Name field, type a name for the volume that appears when you open the disk image.
    4 Choose the size of the disk image from the Size pop-up menu.
    5 Be sure you choose a size that’s large enough to hold any changes and new documents you might add.
    6 Choose an encryption option from the Encryption pop-up menu.
    7 Use the default settings for the rest of the options:
    8 Choose “Mac OS Extended (Journaled)” from the Volume Format pop-up menu.
    9 Choose “Single partition - Apple Partition Map” from the Partitions pop-up menu.
    10 Choose “read/write disk image” from the Format pop-up menu.
    11 Click Save.
    Enter a password, and click OK.
    Disk Utility creates the disk image and mounts its volume on your desktop.
    Copy the documents you want to protect to the volume.
    If you want to erase the original documents so they can’t be recovered, drag them to the Trash and choose Finder > Secure Empty Trash.

  • Moving Address Book to encrypted disk image

    How can I protect the privacy of the content within Address Book and iCal? Would moving those applications to an encrypted disk image be sufficient or are there other related files located elsewhere that I need to be concerned with? Also, what would be the ramifications of not having those applications located within the Applications folder?

    If you put the files on an encrypted disc image, then you will need to decrypt them in order to make changes. Using an encrypted disc image is mostly a method for archival storage.
    You could enable File Vault which will create an encrypted version of your Home folder. This method allows you to access your data on the File Vault protected Home folder.
    If you are the only user it may be sufficient that you simply not allow anyone to know your admin password, and that you log out or shut down when the computer will be unattended. You can also create a new standard account, then log in only to the standard account. The admin account would then only be used to install software and perform other chores requiring admin access.

  • Moving iCal to encrypted disk image

    If I move iCal to an encrypted disk image, will that be sufficent to protect the privacy of the iCal content, or are there other files somewhere on the computer to be concerned about. Also, what would be the ramifications of not having iCal located within the Applications folder. Same question for Address Book.

    If you put the files on an encrypted disc image, then you will need to decrypt them in order to make changes. Using an encrypted disc image is mostly a method for archival storage.
    You could enable File Vault which will create an encrypted version of your Home folder. This method allows you to access your data on the File Vault protected Home folder.
    If you are the only user it may be sufficient that you simply not allow anyone to know your admin password, and that you log out or shut down when the computer will be unattended. You can also create a new standard account, then log in only to the standard account. The admin account would then only be used to install software and perform other chores requiring admin access.

  • Can you resize a encrypted disk image on a sparsebundle disk image?

    I created a 50GB encrypted sparsebundle disk image on my desktop. I named it BOB and also named the encrypted disk image BOB.
    It's now full.
    I've just made it 60GB with Disk Utility.
    I opened it but on trying to copy a 4GB file into it, I got a message saying my sparsebundle disk image is too small.
    Note: Disk Utility says the following:
    BOB sparsebundle is 61.4GB
    mounted volume BOB is 52.1GB
    Hope that's clear.
    Any help would be most appreciated.

    I created a 50GB encrypted sparsebundle disk image on my desktop.
    hdiutil resize -size 60g BOB.sparsebundle
    Result: "resize failed. File or directory does not exist"
    You need to tell hdiutil where to find the target BOB.sparsebundle file. You could either specify a relative or absolute file path in the command itself, or else you could first change the current working directory to the Desktop. So if you wanted to pursue using Terminal, the second way would be to enter this command:
    cd ~/Desktop
    and then try the same hdiutil command again.
    I'm not familiar with the hdiutil command, and I don't know if the above would work. My own feeling is that trying to manipulate an image file by experimenting with hdiutil entails a risk of corrupting the image file and losing its contents, and it is therefore essential to back up the image file first. But if you are going take the time and space needed for a backup, you might as well instead just create a new, empty 60GB (or larger!) sparsebundle disk image, and copy the contents of your old disk image into the new one. This would not involve any risks, and you'd end up with the larger disk image that you wanted. You could then delete the original, if you wished.

  • 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

  • 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

Maybe you are looking for