I need help, folks.
No idea what's going on here.
I have a 1TB drive on which I have created an 800GB encrypted Disk Image.
I've mounted the image on my desktop but my backup software, Déjà Vu, just keeps on failing to write to this Image.
The software is working fine otherwise as I've backed up to other disks, but I want to start having my backed up data encrypted.

I don't want to have to recreate the Disk Image as it took about 7hrs to create this one (due to the level of encryption).
I used Disk Utility to create the Image.

Here's the error message that my software is giving … I know that says that the destination has 0MB available, but I can manually move items in to it and they copy across just fine.
The likely culprit is the "No entry found for '/Volumes/LaCie 1TB'" but in all honesty I've no clue as to how to go about fixing that.
My account has Read&Write access to the Image as well as the disk that the Image is on.

Any help much appreciated.

Mark

My first guess - it's because the volume name has a space in it. That's not being escaped on the command line.

That sounds like the most likely case to me, too.

You can get around this by making a new mount point, and this should do the trick for you:


Line by line, here's what we are doing:
1. Get the device name of the disk
2. make a new folder to mount the device in to
3. Unmount the current device (your account password needed)
4. Mount it again to the folder created in step 3.

You'll need to be an admin user to do that, and it won't persist across reboots...But it should mean you don't have to relabel the volume (which I think would mean recreating the image).

EDIT: It also presumes the file system is HFS(+). If it is not, replace the 'hfs' in step 4 with the appropriate file system type.

Cheers guys.
Ben, before I do all that, could I not just rename the disk to Lacie1TB, eject the disk, re-mount it and then try that?
I'd've done this already but I'm finishing off the tiling in my bathroom and can't at the moment.

Again, cheers guys.

Mark

Changing the name of the disk didn't fix the problem.

Mark

Is the error message the same?

Anything in Console.app for around the time of the backup attempt?

Nope … Just this Mean anything?

Mark

Not to me I'm afraid. I'm off out now, but I'll take a look when I get back

Instead of a disk image, why not just encrypt the drive?

In Finder, right-click on the volume and select “Encrypt ‘Volume Name...’” and fill in your password in the window. You can use Disc Utility as well for this.

The disk name was in quotes, so it should not need escaping. From experience, you only need to escape spaces etc. if the name is not quoted.

Given the error

'/usr/bin/perl5.8.9: bad interpreter: No such file or directory'

It seems the background psync process is looking in particular place for a copy of perl. Could you check if that file does actually exist? Possibly Apple updated perl to a different version and/or you've got something installed which has redirected that to another install in another folder. Have you installed any stuff like fink for example? Or a LAMP/MAMP installation?

I've got ML 10.8.2 here and the copies of perl in that folder are 'perl', 'perl5.10' and 'perl5.12'.

Maybe also see if there's an update to Deja Vu?

Course the 'hack' answer is 'sudo cp /usr/bin/perl /usr/bin/perl5.8.9' but that may get you into trouble later.

This sounds good, but there's other data on the disk, will encrypting the disk as you describe remove this data?

Mark

Correct me if I've misunderstood, but if the actual hard drive is called "LaCie 1TB" and the encrypted disk image file (.dmg) is stored on this drive, wouldn't that error message suggest it's trying to write the backup just to the top level of that LaCie drive, and not the mounted disk image. Hence the error message because there's not enough free space on the drive because of the 800Gb .dmg file on there.

Shouldn't it be looking for...
/Volumes/LaCie 1TB/Disk-Image-Name.dmg

Or, whatever the mounted disk image volume is named (without the .dmg bit?)...
/Volumes/LaCie 1TB/Mounted-Volume-Name

What I'm trying to say is the backup software is trying to write to the free space left on the hard drive, not the mounted disk image. Perhaps. Maybe.

No - unless you format it with encryption (obviously). Try it on a disc that doesn't matter first, or temporarily back up the data on the drive before encrypting just to be sure.

Slightly surprised you haven't already thought of this.

Actually, as the dmg will result in a mounted volume, it will be looking for

/Volumes/Mounted-Volume-Name

Which will behave just like any other mounted volume. There may be problems with needing work space on the LaCie drive if it's at capacity. The other option is to make a sparse image, which can also be encrypted. Sparse images use the space the data occupies, so even if the volume it represents as the capacity of, say, 800GB but the data it contains is only 10GB, the sparseimage file will be around 10GB in size. If, however, you delete 5GB of data, the file will not shrink by that much. It will always occupy the largest size of data it contained, unless you tell your computer to reclaim that space.