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.
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. -
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) -
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
RafI 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. -
Even though I have LCD font smoothing disabled, Mountain Lion still uses it in PDF views, Safari’s location bar, Mail’s message view, and the dialogs for mounting encrypted disk images. Is there any solution to this problem? Also diabled the Smoothing in the SystemPrefs and also via Terminal. Font smoothing is still there. Very annoying, especially in PDF attachments in Apple Mail.
Try feeding Safari a user-defined CSS file with font-smoothing tweaks (including none). The filename and its filesystem location are arbitrary. Use your favorite coding editor.
Safari > Preferences > Advanced > Style Sheet:
Here is an example with all elements uncommented. Pick the one that works best for your Safari viewing and comment out the others:
Preview. Try Preview > Preferences > PDF > Smooth text and line art (uncheck) -
Time Machine Backups of Encrypted Disk Images, Part 2
Hi:
If Time Machine is backing up a hard drive that contains a subset encrypted disk image as part of its contents, and this encrypted disk image is mounted (in an unencrypted state) where the enclosed data has been changed/manipulated in any fashion, what and when does Time Machine backup?
In other words, does the data in the encrypted disk image only change when the encrypted disk image is unmounted? Or is it somehow backed up real time even when the encrypted disk image is mounted on the desktop in an unencrypted state while Time Machine is working?
Sorry I can't explain this very well, but hopefully the gist is clear.
Thanks!
(OS 10.8.2)Time Machine doesn't back up a disk image file while it's mounted, whether encrypted or not.
-
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$ -
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.
MikeYou 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 -
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? -
Backing up to encrypted disk image on an external usb drive
I'd like to use an encrypted disk image on an external USB drive as the target for my Time Machine backups, but it seems that Time Machine will only recognize physical external drives, and not mounted disk images in the "Change Disk..." window.
Is it possible to make Time Machine use disk images mounted from an external USB drive?
Thanks...."Is it possible to make Time Machine use disk images mounted from an external USB drive?"...
Actually, with a few caveats, it is possible.
Just follow one of the many tutorials on the web for creating an encrypted sparse bundle for use with "TimeMachine" on a network volume (i.e. MACaddress.sparsebundle naming convention, password stored to the system keychain, etc.), and then attach the drive locally and select the drive (not the mounted disk image) as the backup drive. As "Glen Carter" reported in another thread on this site, "TimeMachine" is smart enough to know to mount the disk image for backups when the drive is connected locally.
There are caveats for example, - while backups remain automatic, it appears that actually browsing the backups requires that the disk image be mounted manually first, then accessed via the "Browse Other Time Machine Disks…" option.
One caveat to pay particular attention to is what happens when the drive starts to fill up and space becomes limiting - the processes of deleting expired backups and sparse image compaction may not be well integrated, as discussed here:
http://www.flokru.org/2008/03/15/time-machine-backups-on-network-shares-2-possib le-problems/
The article implies that the end result could be deletion of all backups! The article is dated March 2008 but I have no idea whether the issue has been resolved.
Just be advised that it is an unsupported configuration so the extra security will come at the cost of some convenience and potential increase in the chance of data loss. Most users recommend using supplemental backup strategies since the intended purpose of TimeMachine is actually very limited and often misunderstood. Apart from that, it is a rule written in stone that whenever encryption is used, the encrypted items themselves must be backed up. -
Encrypted disk image from ****
So i made an encrypted disk image and forgot the password.
The disk image:
Size: 100 mb
Format: Mac OS X Extended (Journaled)
Encryption: 25-bit AES
Partition: Single partition-Apple partition map
..and no, i didnt save the password on my keychain
...(you can stop laughing now :P )
I´ve been in contact with Apple Care and we spent about 3 hours trying loads of things with no luck.
I know im more or less f*ed, but i know there is a lot of smart ppl on this forum.
If anyone has idea, no matter how crazy, im willing to try it.Hi Worm76;
My suggestion is forget about what was in the encrypted disk image. Write it off as lost.
It would take someone like the NSA to get it back for you and I doubt very much that you have anything in there to interest them.
Allan
Maybe you are looking for
-
Ok, I've had it. I have tried to set up a new theme for my site to hopefully overwrite all material on MobileMe, I am currently in the process of erasing all my site data on the remote disk, and still, when I publish, it goes for a long time, and the
-
Premiere Elements 3.0.2 Quicktime Export Crash
I haven't used Premiere Elements 3.0.2 in a few months, but now I want to export something I was working on as a Quicktime movie. However, whenever I choose the "Quicktime" option from the Export menu, the entire program just closes without any error
-
Ciao, in order to create a VSS cluster is it mandatory to put the C6880-X-16P10G line card in performance mode ? BR, Luciano
-
Header affixed to a text frame, repeared with autofill, Indesign CS3
Hi, Can I affix a text-header to a text frame such that when I use autofill, the text frame will be repeated into the auto-added-pages with the header attached on its top, centered? Can I do it on the Master Page? Best regards, Mickey
-
HT201612 bootcamp reinstall problem
i have already partitioned my mac with bootcamp before and then i deleted it. Now i would like to partition it with bootcamp again but i keep getting an error saying something about not being able to move some things. what can i do?