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.

Similar Messages

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.

R&R Backup (Image) on two external USB drives

Hi Forum,
in the early BIOS state of my T500 and working with Vista I had to rebuild my system several times due to OS failures. For that reason I periodically run R&R and make images on an external USB drive.
Since I'm traveling very much I always have the USB drive with the image with me. The drive contains one basic backup and some incremental backups up to level 25 (at the time being).
Now my goal: in case of a theft or a failure of that USB drive, I want to keep a second image on another USB drive at home.
Now my questions:
1: Is it possible to make backups with R&R (basic and incremental) of one computer on several USB drives?
In that case R&R must detect which incremental level is present on the USB drive and create the appropriate backup (management of the levels on the USB drive, not on the computer).
Example: USB drive A contains one basic backup and some incremental backups to level 12 (consistent) - USB drive B contains one basic backup and some incremental backups to level 17 (consistent as well).
2: If the answer to question 1 is "yes" - does R&R manage this automatically in the windows interface or is it necessary to use the DOS level (rrcmd.exe). Which switches are to be set?
Many thanks for help
Axel

It is a difficult question: the help file isn't entirely clear.
Here is my recent experience: using R&R 4.21 I had backed up my machine to the internal drive + 1 external USB drive several times, so that there was the base back-up and several incrementals on both drives. I also had copied the base backup + earlier incrementals to DVDs using the advanced menu entry for that task, just to be on the safe side. And, using another program (the free version of Syncback by 2BrightSparks), I regularly duplicate documents + pictures to the USB drive, so I'm covered in 3 different ways on 2 types of external hardware.
On one or two occasions I did an incremental backup on the internal drive only--but the next time I did an incremental with the external USB drive attached, the missed incrementals were synchronized onto the external drive.
Now, 2 weeeks ago I decided to zap the main disk and rebuilt the OS + programs to have a "clean slate" for 2010. When I had finished reinstalling everything minus personal files, I made a base backup (the only choice offered) on the internal drive with the external drive attached. This effectively erased the existing earlier backups on the external drive and copied over the new base backup.
So this synchronization only operates in one direction: the external USB drive's store of R&R backups is a replica of what is on the main internal drive.
I strongly suggest trying this all out (i.e. missing an incremental backup on the external drive, then making sure it has catched up after the next incremental backup) after making an external copy on DVD of the R&R backups. In fact, if you have the nerve, the patience and the time (and the DVD backups!), you should also try a bare metal restore of the DVD backup (I did last year when I bought this machine and hadn't too many personal files on it-- R&R 4.21 does actually work!)
sorry i can't be more specific, but my advice is to practice the "disaster recovery" at least once, early on, in order to be sure how it works if disaster does strike.

How to recover after performing an 'Erase' and then 'Partition' within Disk Utility of an External USB drive?

Hi - I accidently ran an 'Erase' and then 'Partition' within Disk Utility of an External USB drive (meant to run it against another drive that was plugged in). Does anyone have any suggestions on if it is possible to recover from this? It has all my family photos on it and my backup is a few months old :-(
I tried running Stellar Phoenix Mac Data Recovery but it found what looks like basic mac folder structure (probably from the first erase). I think what messed me up was that I rain the repartition which formats the drive a 2nd time! Any help is truly appreciated!
thank you,
-Steve

Hello RalphR_MI,
Take a look at this page, which lists several articles. Please let me know if any of these help you restore your backup.
Also, take a look at this article, as well as this one.
I hope this helps. I'm not sure of a few things, so I'm sorry for sending you so much, but I'm confident it will give you something new to try.
Please let me know if this helps. Good luck!
↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓

Problems creating a disk image on an external hard drive

Hiya,
I've been trying to create a disk image on my dad's external hard drive to hold my back-ups all day with no luck. I've managed small ones, e.g. a few MB, but when trying to create images 20 or 40 GB in size (which is what I need), it isn't working.
When I've tried creating them in Disk Utility with the place to save them to as the external HD, it says "Unable to create... Illegal seek" which doesn't explain much to me! I have been successful in creating a large disk image on my own HD, but when I try to move it to the external HD, it says "Sorry the operation could not be completed because an unexpected error occured (Error code -1309)."
Extra info:
- I am saving my back-ups in a disk image, as they must be password protected, so that's why I'm not just copying them over.
- There's plenty of space avaliable on the external HD, so it would seem that isn't the problem.
- The HD is a Freecom Classic SL, connected via USB cable.
Any ideas anyone?
Thanks alot,
Charity

Found the answer. It was formatted for Windows.

Disk Utility Not Formatting External USB Drive

Hello,
I recently upgraded to Leopard.  Around this same time, my company purchased two, 1 Terabyte USB External drives for my coworker and I in the graphics/web development department.  They arrived this morning and we were very excited.
My problem is that I cannot get Disk Utility to erase/format the new, external USB TB drive for use with my MBP.  Disk Utility fails almost immediately with the following message:
"*Disk Erase Failed*
Disk Erase failed with the error:
File system formatter failed."
The options I'm choosing for the Erase are:
Volume Format: MAC OS EXTENDED  (i've even tried the 'journaled' version too)
Name: TB
As soon as I hit 'Erase' I get the error message I listed above.  The volume never mounts on my desktop and does not exist.  I can see the drive itself in the System Profiler, so my Mac sees it, it just can't format it!  I've also made sure all my permissions were repaired, so I'm just a little confused as to why this simple task keeps failing?
Is there some additional, esoteric step that I'm missing?
My coworker was able to get his disk to work because he did NOT have Time Machine turned on yet.  When he connected his new TB drive, Time Machine asked him to format/initialize the disk and he of course said "ok."  I had Time Machine set to use my OLD external USB drive and it's been working great. As of this writing, my coworker is a happy camper. I, however, am not.  I'm not blaming Time Machine, just noting the differences between my coworker's experience and my own. Since the volume is not currently mounted on my machine, I can't format my disk the same way as my coworker has done using Time Machine, since Time Machine doesn't see the volume.
My fear is that the manufacturer (whom I've also contacted and am awaiting their response) will throw this back to a software problem....and the folks on the forum here will point their fingers and say 'hardware problem.'  Ah, the eternal struggle.....who to blame?
Any help or additional troubleshooting tips are greatly appreciated.

This is the best, and only, way to format an external hard drive, which is courtesy of Kappy.
Extended Hard Drive Preparation
1. Open Disk Utility in your Utilities folder. If you need to reformat your startup volume, then you must boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger or Leopard.)
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Click on the Options button, set the partition scheme to GUID (only required for Intel Macs) then click on the OK button. Set the number of partitions from the dropdown menu (use 1 partition unless you wish to make more.) Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the volume(s) mount on the Desktop.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process will take 30 minutes to an hour or more depending upon the drive size.
Steps 4-6 are optional but should be used on a drive that has never been formatted before, if the format type is not Mac OS Extended, if the partition scheme has been changed, or if a different operating system (not OS X) has been installed on the drive.

Any gotchas for encrypted disk images?

I am about to set up e-bills and e-statements at various banks and credit cards and wanted to check a couple of things before doing something that may end up being bad
The assumption I am going with, is I will create an encrypted disk image to store all the PDF's.
1. Is that the right thing to do? Or is there a better way to keep the data secure?
2. If I do so, what is the backup impact? Can I simply set up a task to copy and paste the entire disk image to my external drive?
3. If I want to open the disk image on another computer, can I? How will it authenticate the user/pass on a different computer?
4. I can backup an encrypted disk image to a FAT-formatted external drive?
5. And finally, I have read disclaimers that if I forget the password the data is lost irretrievably. But also, that the password is stored in keychain. So if the password is stored in keychain, the worst-case scenario can only happen if I forget the master password, right? I don't need to truly remember the password to the disk image necessarily, right?

baltwo wrote:
Your profile info indicates that you're running Tiger. If so, post to those forums. If you're running Leopard, update your profile info. What are you trying to protect and from who? Is your computer secure?
IIRC, encrypted disk image passwords are independent from Keychain Access. So if you forget it, then you're hosed. BTW, that's the major failing with encrypted anything. If you forget the password, you're hosed. If the disk image gets corrupted, it's useless with or without the password. Anything stored in an encrypted disk image needs to be backed up in an unencrypted state and stored in some kind of physical thing like a safe. Methinks your a bit paranoid. Disable auto-login, use high-level passwords (that you remember), don't enable the root user account or activate a master password, and you should be secured enough.
I updated the profile. I am running Leopard. So this is the correct forum.
What am I trying to protect? I thought I put it in the first line - statements from banks and credit cards.
From whom? From unwanted entities who may get access to my computer, in any way.
I didn't get the part about the safe. Can I or can I not back up an encrypted disk image to an external drive "as is"? What about possibly opening it up on another computer? And how about putting it on a FAT-formatted disk? I repeat my original questions, but for a reason - they seem to have not been answered.
I do not have auto-login, and I remember my strong login password. I don't have my root account enabled. Under this scenario you think my data is going to be secure? What about if someone were to get control of my computer? Forgive me on this one, I am a switcher so there is a general paranoia about such things which I would like to clarify before reorganizing my life.

Making encrypted disk image takes hours?!

Before I made a Time Machine backup, I wanted to use Disk Utility to create an encrypted disk image on an external hard drive. This way, my computer backup is password protected.
So I set the file for 200G at 128 bit encryption.
That was 12 hours ago. According to the progress bar, Disk Utility is still only one-quarter done with creating the disk image.
Is it normal for Disk Utility to take a full day (possibly two) to create a disk image of this size? Is there any way to create a password-protected disk image quicker? (And, for what it's worth, the external drive is formatted for Mac OS Extended, Journaled.)
Thanks for any advice on this...

Hi, and welcome to the forums.
I'm not quite sure just what you're trying to do.
Are you planning to have Time Machine back-up to that encrypted disk image? If so, that's not going to work. When you start Time Machine, it will create a Backups.backupdb folder on whatever drive or partition you select, then place it's backups in that folder, not in a disk image.
If you want to encrypt your whole home folder, you can use File Vault (System Preferences > Security > File Vault). That will encrypt your entire home folder. But that's almost certainly vast overkill, and has many complications of it's own. Read up on it thoroughly before deciding to do it.
If you have a few files that you want to encrypt, create a (smaller) encrypted disk image on your internal HD, in your home folder. Then copy the documents into it, and securely-delete the originals.
Then TM can back-up your entire system "as is" -- without the overhead of encrypting OSX, your apps, configuration, and everything else in your home folder, but the disk image (and it's backup copy) will still be encrypted.

Indexing of encrypted disk images permanently disabled in 10.8?

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

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

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 creation slow?

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

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

Encrypted disk image creation very slow-

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

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

Encrypted Disk Image 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.

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$

Backing up to encrypted disk image on an external usb drive

Similar Messages

Maybe you are looking for