Failed to mount using disk images? [Archive]

View Full Version : Failed to mount using disk images?

dyoken

03-28-2007, 04:56 PM

I am preparing to set up a computer to backup over the network, but decided to connect the computer directly to the backup drive for the initial backup before setting it up on the airport extreme.

So I am doing a smart update using a Disk Image on the network volume, but everytime I try to do this, I get an error "Failed to mount MacBook Pro Backup" on the second line under Part 1.

Then looking in the log, it says:

...

| 04:48:13 PM | Info | ......COMMAND => Mounting MacBook Pro Backup
| 04:48:13 PM | Error | 2007-03-28 16:48:13.133 hdiutil[349] CFLog (21): dyld returns 2 when trying to load /Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/MacOS/VirtualPCDiskImagePlugin

This last line is in red.

I have no idea what to do. Virtual PC is not loaded on my computer, and I tried to deleted the referred to plugin file, but that didn't help.

Any help would be greatly appreciated!

Dave

dfbackup

03-28-2007, 05:16 PM

dnanian

03-28-2007, 06:37 PM

OK. Delete /Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle and restart. That's a leftover from Virtual PC that's not Intel compatible.

dfbackup

03-28-2007, 06:46 PM

That worked. Thanks for the quick reply.

dyoken

03-28-2007, 08:49 PM

Deleting that specific file was the first thing I did, but it didn't resolve the problem unfortunately...Any other suggestions perhaps? And do you have any insight into why SD! would call up a plugin relating to outdated legacy software when it tries to mount a disk image?

Thanks in advance for your help with this.

Dave

dfbackup

03-28-2007, 10:04 PM

So you are saying even when you deleted it you still got the error that the plugin could not load? Very odd. I did retart after I deleted mine but that is all I did and now it works fine.

dnanian

03-28-2007, 10:25 PM

I'd need to see the error you're getting, Dave.

dyoken

03-29-2007, 05:34 PM

Not a problem. I will get it to you as soon as I can. Thanks Dave!

RAmeeti

03-31-2007, 01:31 AM

dfbackup

03-31-2007, 01:56 AM

I get this same error whenever I try to have SD mount a network drive for a schelduled copy. For some reasons my computers will only mount network shares if not schelduled. To get around this I include an applescript to mount the netowrk drive through an alias first and all works good. I copied below waht I posted in another thread:

*****************************

I have this same issue on my two macs (PPC & Intel) with a network backup. I use this applescript to mount the drive. It opens an alias (in my ~/Library/Favorites) I have stored to the network drive. As long as you have the user and pass stored in the keychain this will require no user input. Just replace the "alias-file-name" below with the name of your alias in your favorites folder. The script will input your correct username.

set thePath to ((get path to startup disk) & "Users:" & ¬
(do shell script "echo $USER") & ¬
":Library:Favorites:alias-file-name") as string

tell application "Finder"
open alias thePath
activate
end tell

And then I use this script to unmount it. Be sure to put the name of the network drive here, not the alias name.

tell application "Finder"
try
eject disk "name-of-network-disk"
end try
end tell

You can add these directly into CopyJob.applescript inside your schelduled backup package. Just don't forget to toggle the checkbox for the script inside the SuperDuper! interface to recompile the script.

dnanian

03-31-2007, 07:48 AM

RAmeeti

03-31-2007, 11:04 AM

Your issue is likely because the "path" to the image (/Volumes/10.0.1.100/Backups) has changed, whether because its IP address has changed or something else has been renamed.

I'd suggest giving the host an actual hostname and using that, then recreating the schedule (or re-selecting the image).Good thoughts as I see by the path that I've got a problem. But ...

Reality is that 10.0.1.100 is a statically mapped NAS (Networked Attached Storage) drive. The drive has a host name of NAS-500. It has 3 shares on it. One of them is 'Dad'.

I use 'Connect to Server ...' to mount it via 'SMB://10.0.1.100' and then I get the selection option of the 3 shares. I select 'Dad' and it then mounts as Volume 'Dad'. Within that volume, there is a single folder named Backups. With that volume already mounted, I attempt to do my SD backup but the error occurs as noted.

I have tried to connect to the drive by using 'SMB://NAS-500/' but that does not work. I get an error -36 but my thoughts are that since the drive is statically mapped, and since it is already mounted, if I could manually select my Target Image as /Volumes/Dad/Backups/Portable Backup.sparseimage then all would be fine. But SD is putting the drives IP as the Volume name instead of 'Dad' which is what the Finder is showing and which is the real volume name. It does look like SD is not recognizing the volume name that is part of the location process that is accomplished via the Save As... dialog when using a Sparse Image file.

More ideas? and thanks for your help.

dnanian

03-31-2007, 12:03 PM

RAmeeti

03-31-2007, 12:15 PM

dnanian

03-31-2007, 12:25 PM

No -- not in "Save As". Mount the sparse image by double-clicking, then select its volume directly in the destination pop-up.

RAmeeti

03-31-2007, 12:33 PM

No -- not in "Save As". Mount the sparse image by double-clicking, then select its volume directly in the destination pop-up.Ok. Sorry but I may be a bit dense here.

There is no sparse image to select until SD creates it (or so I think.) I used the 'to' to select 'Disk Image...' which then allowed me to get to the 'Save As...' where I did that so that I would theoretically have an empty sparse image file but going through the Finder, I don't yet see any sparse image file to select because SD hasn't really yet created it. Am I missing something here? Or am I supposed to be able to pre-create this sparse image in another way?

RAmeeti

03-31-2007, 12:42 PM

Ooops. I thought it was time to reread the documentation and within that I quote:

"It's very important that the network drive support files larger than 4GB. FAT32-based servers or NAS drives will not work, and fail pretty spectaculary when this limit is reached. Please ensure that the network volume is HFS+, NTFS or ext3 all of which support large files."

Given the above, my wishes for using a NAS drive are pretty much shot down I guess. I did mention that I was using a NAS setup in my original post but we all missed it.

dnanian

03-31-2007, 12:43 PM

No, a NAS works fine: it's a FAT32 NAS (or servers) that won't work.

Is yours formatted FAT32?

RAmeeti

03-31-2007, 02:12 PM

No, a NAS works fine: it's a FAT32 NAS (or servers) that won't work.

Is yours formatted FAT32?I'll trust your saying that a NAS will work even though it is specifically stated that NAS will not work per my quote above.

Moving forward though, yes, my NAS is formatted FAT32. :-( I guess this is done in the interest of the greatest availability to users. Not quite sure what to do at this point though since I want to access it from my Macs and from my PC, kinda the whole point of having a NAS. FAT32 is the only one that is truly cross compatible. Ugh. Am I wrong on this?

dnanian

03-31-2007, 03:17 PM

I actually wrote the User's Guide, and it's a confusing sentence. What I was saying was that you can't host images on drives that won't support >4GB files, nor will it work with protocols that don't support large files.

So, NAS devices and servers that don't support these things won't work.

You don't need to format a NAS as FAT32 to access it with a PC. That's part of what the network protocol abstracts. After all, you can access your Mac's HFS+ formatted drive from a PC, right?